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
Do not fail rubocop when using in generator #961
Conversation
Can you update docs/modules/ROOT/pages/usage.adoc as well? |
@koic thanks for your review. I incorporated your feedback. |
This looks good to me. Can you squash your commits into one? |
I did all changes in-browser. Could you squash directly when merging this pull request? See screenshot at https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request#merging-a-pull-request |
I know squash merge but I don't prefer it:
I'm in no rush to merge, so please squash when it's convenient for you :-) |
Without this, the generator would exit with an error, if it found any warning or less severe offenses. Related to rubocop#956
Ok, understood @koic. I squashed them. |
Thanks! |
Files not supported by rubocop would lead to an error, which in turn would mean that the rails generate command would fail. We are going to filter the files to ensure unsupported files are not sent to rubocop Followup for rubocop#961 and rubocop#956
Files not supported by rubocop would lead to an error, which in turn would mean that the rails generate command would fail. We are going to filter the files to ensure unsupported files are not sent to rubocop Follow-up for rubocop#961 and rubocop#956
Previously, the 'rails generate' command would send unsupported files to Rubocop,causing errors and failures in the process. To fix this, we added a filter that only sends parsable files to Rubocop. This commit updates the documentation to reflect this change, helping users avoid errors and complete 'rails generate' command successfully. Follow-up to rubocop#961 and rubocop#956
Previously, the 'rails generate' command would send unsupported files to Rubocop, causing errors and failures in the process. To fix this, we added a filter that only sends parsable files to Rubocop. This commit updates the documentation to reflect this change, helping users avoid errors and complete 'rails generate' command successfully. Follow-up to rubocop#961 and rubocop#956
Without this, the generator would exit with an error, if it found any error or warning