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
When exposing the ports of a process one would expect that the receiving port namespace would not just inherit the ports but also the mutable properties of the donor PortNamespace, such as the default, valid_type, help, validator and required attribute. Currently this is not the case. Additionally, any newly created namespaces will just receive the default properties. It would be good if both the inherited properties as well as those of a newly created namespace could be overridden from the expose call itself.
The text was updated successfully, but these errors were encountered:
sphuber
changed the title
Allow PortNamespace created through exposure to be marked as non-required
Overload the mutable properties of a PortNamespace when exposing it
Jun 8, 2018
When exposing the ports of a process one would expect that the receiving port namespace would not just inherit the ports but also the mutable properties of the donor PortNamespace, such as the
default
,valid_type
,help
,validator
andrequired
attribute. Currently this is not the case. Additionally, any newly created namespaces will just receive the default properties. It would be good if both the inherited properties as well as those of a newly created namespace could be overridden from the expose call itself.The text was updated successfully, but these errors were encountered: