-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
Refactor: Switch out ~ expression in tag for not statement #935
base: main
Are you sure you want to change the base?
Conversation
Hi @mvz EDIT: Somethings up with the project structure and I can't. So I figure someone else will need to. |
@luke-hill one thing that makes the PR fail is the change in quote characters in Perhaps I need to adjust the RuboCop config so it matches up with the rest of Cucumber. Suggestions welcome! |
In terms of styling. We use single quotes in all ruby projects. Also we don't adhere to the gemspec rule about dev dependencies in the gemfile (No idea why that's a default). I can amend the quotes. I think I clicked something in my editor for that, as I didn't use rubocop on the CLI. The other one I've no idea on though |
@luke-hill allright, here's my plan:
|
Hi @luke-hill, I have finally done the second step in my plan above. Could you please rebase your branch on current main? |
Will do. It's also made me think we should have an overall cucumber style for rubocop as a separate gem that way it saves the hassle of setting things up each time. But I'm not sure when I'll get around to it. |
That's a good idea and will help a lot to make the settings more consistent. |
Summary
Switch out legacy tag expression syntax - This is needed to fix up some tech debt in cucumber (Which sanitizes it)
Details
As written above
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist: