Allow an application user to choose a different key-missing behavior
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 28
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when a key is missing, it returns a default empty value (i.e. empty string, zero), but this might hide a configuration bug, and specially in development environment, it could be desirable to throw an exception instead (like MissingKey).
This change should be backwards-compatible.
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 key-missing lookup and the existing MissingKey behavior in the Java codebase. Define how an application selects the new behavior while preserving the current empty-value default, then add coverage for both modes and verify that missing keys produce the selected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100