-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add optional attr support #75
feat: add optional attr support #75
Conversation
Oops, checks on node 12 failed, probably because I used |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @tivac. The code changes looks pretty good already, I just have two suggestions for improvements.
Oops, checks on node 12 failed, probably because I used
??
. I'll update here in a bit.
Thanks for pro-actively updating based on the CI results!
Co-authored-by: Eric Cornelissen <[email protected]>
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Co-authored-by: Eric Cornelissen <[email protected]>
🎉 This PR is included in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes #74
Adds support for appending a
?
to the end of an attribute config entry to make it optional. Optional attributes will be checked if they exist, but if they are missing andrule::whitelist
is set it will not fail validation.I'll update docs once this looks good to a maintainer.