Overriding enum values doesn't work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
Consider the following enum:
#[derive(Deserialize)]
pub enum Config {
Case1 {
field: bool,
},
Case2 {
field: String,
},
}
It becomes impossible to override the value of Config in through overlaid sources leading to "value of enum Config should be represented by either string or table with exactly one key". I would like to be able to provide a default value for this configuration but have a later, more specific bit of config override this. Is this a change which would be acceptable?
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.
Research direction
No file, test, or entry point is named in the issue. Start by locating the overlay handling for enum values; done means a later, more specific configuration source can replace a default enum value without the reported representation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100