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
For cases where a parameter needs to be added as child of another parameter or node as part of "building" a model from a schema. The current approach requires making a unique global name which has issues with risking conflict and create horrible names.
We currently model this in nodes using "sub-names"; an optional unique identifier in the namespace of the parent node name. The same idea could work with parameters.
However, I wonder if it would make more sense to have an optional parent (and whether the nodes should be re-modelled in this manner also).
Core Parameters can now be identified with an optional parent
string. This is helpful for creating Parameters in compound
nodes without risking naming conflicts with the user's own
parameter names.
Fixes#179.
Core Parameters can now be identified with an optional parent
string. This is helpful for creating Parameters in compound
nodes without risking naming conflicts with the user's own
parameter names.
Fixes#179.
For cases where a parameter needs to be added as child of another parameter or node as part of "building" a model from a schema. The current approach requires making a unique global name which has issues with risking conflict and create horrible names.
We currently model this in nodes using "sub-names"; an optional unique identifier in the namespace of the parent node name. The same idea could work with parameters.
However, I wonder if it would make more sense to have an optional parent (and whether the nodes should be re-modelled in this manner also).
See also discussion in #107
The text was updated successfully, but these errors were encountered: