Skip to content

required:False does not apply when exposing outputs for a specification without namespace #269

@bastonero

Description

@bastonero

plumpy behaves in the following when exposing outputs for a specification process (example as in AiiDA WorkChains):

  • Define a MainWorkChain
  • Using a SubWorkChain/SubCalcJob: spec.expose_outputs(SubWorkChain, namespace_options={'required': False})
  • MainChain.spec().outputs will still retain the required (True) outputs of SubWorkChain

The same doesn't happen when specifying a namespace in the expose_outputs.

Personal comments: I would expect as a plugin developer to actually override all required options of the exposed outputs, even when not defining a namespace. Otherwise, it seems pointless to specify the namespace_options if this does not happen (?).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions