-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Users should be able to globally configure example group and includes language #333
Comments
It also happen with permissions :create?, :can_create_package_in?, :unlock? do
it { expect(subject).to permit(user, project) }
end
permissions :local_project_and_allowed_to_create_package_in? do
it { expect(subject).to permit(user, project) }
end Just seen it in Rubocop 0.58.2 |
As @backus mentioned above, we’d have to make a configurable list of DSL aliases, and stick to using that list of aliases throughout our cops. |
Additionally, I imagine a cop that would specifically watch over Not sure how to deal with aliases defined in specs directly, does Language have to track that dynamically? |
Have the same issue with pundit. Is it going to be released? |
@denys-husiev There's nothing to release yet. A proof-of-concept is WIP now #894, you may jump in if you'd love to help. And after we would still need to make the rest parts of the Language module to be configurable. Any help on this front is much appreciated. |
I made some POCs here: #921 (comment). |
@sl4vr Thanks a lot! |
Yet another case that could be improved https://github.com/rubocop-hq/rubocop-rspec/pull/858/files#r365795088 |
As described in #321, if a user has some custom DSL in their specs then a handful of cops produce false positives. For example
In RSpec you can do something like this
and of course since it is plain old ruby you can do something like this (not sure if this would specifically work)
To handle stuff like this properly, we should support something like this
which all cops would respect.
The text was updated successfully, but these errors were encountered: