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
{{ message }}
This repository has been archived by the owner on Jan 9, 2019. It is now read-only.
Well this was for 'enabled','disabled','pending',etc. This allows people to build nodes without putting them into service as well as providing quick search without nested queries and/or lots of joins . Highly recommend not moving since this can be future function if not ready to enable yet but should be at this level in the tree.
It would be impossible by the way to build a node without putting it into service without building said attribute; with status IN node, you have said ability. You would have to build out the node to provide this capability first in the model you are describing. By default, this exists in current model.
You would still need to be able to create the node and have it in a holding pattern without having to create any attributes, IMHO. Otherwise you are stating to users that this attribute has to be created EVERY time which is an annoyance.
Remove the status property from the Node domain class. An attribute can be defined for users interested in a property like status.
See #169
The text was updated successfully, but these errors were encountered: