simp / simp/rubygem-simp-scelint
null values in checks should be an error
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 3
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 5
Description
A value of null in a check should trigger a warning since Hiera will just ignore the value as not set.
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 tracing the linter's check validation path for values that are null, then find the existing tests for check warnings. Add coverage showing that a null value produces a warning rather than being silently ignored, and run the relevant test suite to confirm the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100