You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems now that reading expressions requires again that Universe be specified upon loading them. After an initial refactor of Meaning, it looks like Universe had not been required for loading Meanings for a bit. Since Expressions need a meaning, this means that requiring Universe in Meaning once again means that loading expressions requires defining a Universe in a function that loads / reads the expressions. However, because Expression has a Universe as an attribute, it is saved in the yaml dump and should not need to be specified as an argument in functions that load expressions.
A potential solution could be to load the first Expression's Universe attribute in read_grammatical_expressions and use that instead of passing universe as an argument in that function.
The text was updated successfully, but these errors were encountered:
It seems now that reading expressions requires again that Universe be specified upon loading them. After an initial refactor of
Meaning
, it looks likeUniverse
had not been required for loadingMeanings
for a bit. SinceExpressions
need a meaning, this means that requiringUniverse
inMeaning
once again means that loading expressions requires defining aUniverse
in a function that loads / reads the expressions. However, becauseExpression
has aUniverse
as an attribute, it is saved in theyaml
dump and should not need to be specified as an argument in functions that load expressions.A potential solution could be to load the first
Expression
'sUniverse
attribute inread_grammatical_expressions
and use that instead of passinguniverse
as an argument in that function.The text was updated successfully, but these errors were encountered: