QoL symmetry: `Run.inputs` mirroring `Run.outputs`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- backend-api-design
Research direction
Start by locating the Run class and reading the existing Run.outputs property to understand its shortcut and surrounding conventions. Add the corresponding Run.inputs property with matching behavior, then verify that it provides the requested label:value dictionary for inputs.
Written by the indexing model from the issue text.
Description
Because I'm discovering that sometimes I want a simple label:value dict for the inputs as well as the outputs and for basically the same reasons. Run.outputs is just a property shortcut, so this is an easy symmetry to add.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pyiron/flowrep
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
API
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100