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
Implement unambiguous keywords #2043
Comments
Cool, I'm in favour of this proposal. We have an issue in What I'd propose in order to get this to a point where we have an on/off flag for unambiguous keywords is:
One thing we should discuss is how the option should be surfaced. We already have strict mode, I would see this as another facet of that but that would be a breaking change since strict mode is on by default. I do believe this is a good default for Cucumber, it's just how best to roll that out. |
For 2, I think could have an option If we eventually merge this into strict, I'd think the following would be my eventual ideal (where strict is default for both)
Think it would be better with separate options flags so users can opt out of things they don't care about (but don't opt out of extra behavior they are okay with at the same time) |
@mattwynne I think this might be a good candidate for the new contributors ensemble. It's not super heavy in terms of complexity but would touch a lot of different parts of the codebase and give a good mapping of the architecture. What do you think? I'd be happy to draft a feature file so there's somewhere to start. |
I am against the removal of Your idea works nicely for the English language, but not for some other. In German, the sentence structure after |
While I still think |
@iomedico-beyer thanks for highlighting that perspective on the German language. At this point it looks unlikely we will enforce strict keywords, at least any time soon if ever. So we could keep |
As described in cucumber/common#768
The text was updated successfully, but these errors were encountered: