-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 support for Tag Expressions #1003
Comments
@aslakhellesoy I am quite new to the project, but I would be happy to give this feature a try. What do you think? |
That would be fantastic! The first step would be to port the TagExpressions library to Ruby. See cucumber/common#60. It's a tiny codebase! Just use the JavaScript or Java code as inspiration. When that's done, send a PR to
How does that sound? |
Sounds good, thanks a lot @aslakhellesoy :) I am planning to dedicate some times next week and keep you updated here. |
That's great @nodo - let us know if you have any questions. You can also try the contributors chat room. |
If someone wants to take a crack at integrating @nodo's work in cucumber/common#67, I'd like to ask that they help us to stay backwards-compatible for one major release by making the choice of old / new tag expression syntax a configuration option. That will enable us to transition users over to the new syntax gradually. We can make it opt-in first, then make it the default for the next major release. |
Great work so far @nodo! I have released cucumber-tag_expressions 1.0.0! |
I second @mattwynne's comment about backwards compatibility. In the next version, use the new
Also, print a deprecation warning in the other case, telling people that:
WDYT? |
Sounds good @aslakhellesoy , I will give it a try and keep you updated. Thanks for the hints. |
Automatic identification of legacy tag expressions (with a deprecation warning) would be awesome UX if we can achieve that. Remember tags are used in hooks as well as on the CLI. |
Hi @nodo did you make any progress on this? |
@aslakhellesoy not yet, after seeing added to milestone 4.0 I thought to concentrate on #954. I would like to pick it up asap though. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Tag Expressions is a more intuitive way to specify tags in tagged hooks and on the command line's
--tags
argument.Expected Behavior
Tagged Hooks should accept a single string:
Likewise, the
--tags
command line argument should allow the same. (Specifying it more than once should cause an error)Context & Motivation
The current mechanism to specify
or
with comma andand
with multiple--tags
is incredibly awkward. Tag Expressions are intuitive!The text was updated successfully, but these errors were encountered: