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
The problem is that trying to call a setter of a derived field (some people do it when using matchstick) crashes on deployment because derived fields are supposed to only be derived from other entities and not be set ever.
The text was updated successfully, but these errors were encountered:
@evaporei@azf20@dimitrovmaksim This just bit me - I was migrating away from manually setting a field to deriving it, and thought that building the graph would result in a compile error if a setter was being used anywhere. Turns out I missed removing a setter in one place, but only found out about it when the deployed graph had errors.
The problem is that trying to call a setter of a derived field (some people do it when using matchstick) crashes on deployment because derived fields are supposed to only be derived from other entities and not be set ever.
The text was updated successfully, but these errors were encountered: