puppetlabs / puppetlabs/puppet-resource_api
Missing verification that a type has namevars
Open
Nobody has claimed this yet.
bug
- Dominant language
- Ruby
- Stars
- 27
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
There is currently no validation check that a type has (a) namevar(s). When a type without a namevar is loaded it leads to a plethora of "fun" and unhelpful exceptions.
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
Start by locating where resource types are loaded and where namevars are represented or validated. Add a check that rejects types without at least one namevar with a helpful error, then add or update a test covering a type with no namevar and verify that the confusing downstream exceptions no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100