`save_config` should let you create missing scope id at lowest scope
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Look at the save_config function in the codebase to understand how scopes are handled. The issue describes three scenarios for creating missing scope IDs. Start by reading the existing tests for save_config to see current behavior. Then, implement the logic for creating missing scopes when allowed, and update the missing example in the README. Verify changes by running the project's test suite.
Written by the indexing model from the issue text.
Description
When saving a config to a single scope, when passing in a scope-id that does not exist, it should create it if you allow it.
When saving a config to multiple scopes where the the lowest scope-id does not exist and append_new_fields_to_last_scope is true, it should create a new scope and append all new fields to this scope if you allow it.
When saving a config to multiple scopes where one scope-id does not exist and it is not the lowest scope, it should be an error.
We should additionally update the missing example. The main use-case is being able to perform scope-specific calibrations (tied to the hostname or subject) for a specific instance and then save back overrides specific to that scope-id.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 AllenNeuralDynamics/ficus
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AllenNeuralDynamics/ficus#87 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AllenNeuralDynamics/ficus#85 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AllenNeuralDynamics/ficus#84 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
AllenNeuralDynamics/ficus#54 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
AllenNeuralDynamics/ficus#86 ·
All issues in AllenNeuralDynamics/ficus
Similar issues
-
pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8843 ·
Maintainers usually reply within 1 day
-
breaking change enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sktime/sktime#11310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day