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
A legacy implementation is the project prototype. On the one hand this is a very neat way to add derived properties to an object (easy to interpolate), on the other hand it is somewhat of a hassle.
Right now the project prototype is only attached when needed: the reducer copies to an object literal. This is confusing since specific project properties are not always present.
We can either move all the project getters and setters to separate selector functions, or move the prototype down all the way and have the reducer clone the project with the prototype.
I think selectors are not the best solution in this case since it separates project properties to multiple files.
The text was updated successfully, but these errors were encountered:
A legacy implementation is the project prototype. On the one hand this is a very neat way to add derived properties to an object (easy to interpolate), on the other hand it is somewhat of a hassle.
Right now the project prototype is only attached when needed: the reducer copies to an object literal. This is confusing since specific project properties are not always present.
We can either move all the project getters and setters to separate selector functions, or move the prototype down all the way and have the reducer clone the project with the prototype.
I think selectors are not the best solution in this case since it separates project properties to multiple files.
The text was updated successfully, but these errors were encountered: