-
Notifications
You must be signed in to change notification settings - Fork 504
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
Schema test/not accepted values #284
Schema test/not accepted values #284
Conversation
d198c6b
to
f60eebc
Compare
Just did a small rebase on your branch so that we don't have merge conflicts! This is really great — I'm still thinking a little about the name here: is "not accepted" best, or is something like disallowed, or barred, better? |
When I was looking for this functionality I was mainly searching for "not accepted values", but disallowed or rejected for example could be fine too! I would say that barred seems less familiar to me, but up to you! |
The more I sat with it, the more I thought "not allowed" felt very descriptive, let's merge! |
Schema Test - Not accepted values, test fixed empty lines at the end Update changelog
Schema Test - Not accepted values, test fixed empty lines at the end Update changelog
Schema Test - Not accepted values, test fixed empty lines at the end Update changelog
This is a:
main
)Description & motivation
This is a new macro that will allow us to check
not accepted values
, exactly the opposite ofaccepted_values
.I'm already using it in a table with users and roles where I want to ensure that some roles are not inside that table.
This will close #283
Checklist
I have a doubt about testing this kind of macros, writing a test that uses the macro only tests when it works, but not when it fails. Is there any way of testing when it fails?
Also, this is my first PR, I hope I did everything ok 🙂