SubsystemBuilder does not allow options specification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
If the user creates their own variable_meta_data for their subsystem, the builder doesn't reflect any of those options. The subsystemBuilder should be a singular place that users, or an AI, can go to determine all interfaces to everything inside that subsystem.
Issues Resolved
New user confusion on which options should be set.
Issues Unresolved
Where do I set options (ideally in the .csv file). Maybe we need to tell users to do this somewhere in the Docs?
Suggested implementation.
Add a method to SubsystemBuilder to return any variable_meta_data file the user specifies in that subsystem.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the SubsystemBuilder entry point and tracing how a user-specified variable_meta_data file is handled. Check existing tests or examples for subsystem interfaces, then confirm completion when the builder exposes the specified metadata and options consistently; determine whether CSV usage also needs documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100