Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

null values in checks should be an error

Open
#40 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
devtools

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.

Description

A value of null in a check should trigger a warning since Hiera will just ignore the value as not set.

Dominant language
Ruby
Stars
0
Forks
3
Avg merge
2d 15h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from simp/rubygem-simp-scelint

All issues in simp/rubygem-simp-scelint

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.