Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate ProcessSpec to use PortNamespaces #1096

Closed
sphuber opened this issue Feb 1, 2018 · 1 comment
Closed

Migrate ProcessSpec to use PortNamespaces #1096

sphuber opened this issue Feb 1, 2018 · 1 comment
Assignees
@muhrin @sphuber
Labels
priority/important topic/workflows type/accepted feature approved feature request
Projects
Engine
Milestone
v1.0.0

Comments

@sphuber
Copy link
Contributor

sphuber commented Feb 1, 2018

This is a sub problem of issue #660 . In order for the exposing of inputs to be implementable, the ports of the ProcessSpec, first need to become proper namespaces. This will be implemented in plum. Consecutively, the input_group can be replaced by a proper PortNamespace for the implementation of the spec of a JobProcess that wraps a JobCalculation that has use methods with an additional parameter.
@sphuber sphuber added this to the v0.12.0 milestone Feb 1, 2018
@sphuber sphuber added this to In Progress in Engine Feb 1, 2018
@sphuber sphuber mentioned this issue Feb 1, 2018
Merged
@sphuber
Copy link
Contributor Author

sphuber commented Feb 5, 2018

This was fixed in PR #1099 and also takes care of issue #919

@sphuber sphuber closed this as completed Feb 5, 2018
Engine automation moved this from In Progress to Done Feb 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@muhrin muhrin

@sphuber sphuber

Labels
priority/important topic/workflows type/accepted feature approved feature request
Projects
No open projects
Engine
  
Done
Milestone
v1.0.0
Development

No branches or pull requests
2 participants
@muhrin @sphuber