-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add ability to ignore certain namespaces #173
Comments
Thank you for suggesting this! We can add support for some patterns there. What syntax do you prefer the most? For example, |
If it is possible to pass a Ruby regex in the Yaml file, that would probably be the easiest. Then you wouldn't have to implement any custom pattern parsing yourself. |
Sounds fair! I will look into that. By the way, would you like to contribute? I would be happy to help you and release it as soon as possible. |
I'm sorry it took me so long to implement this feature. Nevertheless, it's finally done, and if you're still using the gem, you can clean up your Released in 1.7.11. P.S. Fixed |
You can follow this wiki for precise syntax: https://github.com/djezzzl/database_consistency/wiki/regexp-support-in-configuration. |
There are cases, where it would be nice to have a more comfortable method of ignoring multiple models or attributes at once in the config.
I have one case where the namespace
DataMigration
contains models that are not used in production and are kept for historic reasons. So I currently have 44 lines of the following in my config:I have another case where errors are "inherited" from another gem and I have 13 lines of the following in my config:
Being able to ignore all attributes starting with
thredded_
(per model or even globally) would be nice.The text was updated successfully, but these errors were encountered: