'hintsFile' should be close enough!
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 487
- Forks
- 200
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 2
Description
If an option in an ior config file is a unique match to an IOR option, IOR should allow it (maybe with a warning?)
If i say "hintsFile=/foo/bar/baz", IOR should know I meant "hintsFileName"
Bonus points: misspellings should be allowed too. Something like git's "autocorrect" option
you said "colective"; assuming you meant "collective" would be nice.
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
The issue names no files, tests, or entry points. Start by locating how IOR parses configuration options, then determine how unique abbreviations, warnings, and misspelling correction should interact. Done means the requested matching behavior is specified and covered for the hintsFile/hintsFileName example and the proposed autocorrection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100