git-ecosystem / git-ecosystem/trace2receiver
investigate YML ruleset parsing
Open
@jeffhostetler is already working on this.
Since Apr 15, 2024.
- Dominant language
- Go
- Stars
- 61
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
We were expecting that a undefined section in the YML would cause an error, rather than silently being ignored. Is there an option for this in the YML parser and/or do we need to validate the resulting dictionary for unknown/unexpected keys?
https://github.com/git-ecosystem/trace2receiver/issues/24#issuecomment-2027717356
This is not urgent, but it would be nice to avoid such confusion in the future.
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.
Assessment
This issue has not been assessed yet.