fix: fixing chalk custom keys validation - Githubissues

crashappsec / chalk

Chalk allows you to follow code from development, through builds and into production.

https://crashoverride.com/

GNU General Public License v3.0

348 stars 15 forks source link

fix: fixing chalk custom keys validation #307

Closed miki725 closed 4 months ago

miki725 commented 4 months ago

[x] Followed the steps in the contributor's guide: https://crashoverride.com/docs/other/contributing#filing-the-pull-request
[x] PR title uses semantic commit messages
[x] Filled out the template to a useful degree
[x] Updated CHANGELOG.md if necessary

Issue

key validation enforced custom keys to start with X- or _X- which is invalid con4m syntax. Changing to X- and _X_.

Also adding test case how custom keys can be added to reports and chalk marks.

Testing

➜ make tests args="test_config.py::test_custom_keys"