Skip to content
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

meta: Rule support across Cucumber implementations #869

Closed
davidjgoss opened this issue Jan 21, 2020 · 11 comments
Closed

meta: Rule support across Cucumber implementations #869

davidjgoss opened this issue Jan 21, 2020 · 11 comments
Assignees
Labels
📖 documentation Improvements or additions to documentation 🧷 pinned Tells Stalebot not to close this issue

Comments

@davidjgoss
Copy link
Contributor

davidjgoss commented Jan 21, 2020

A central issue to track state of support for Gherkin's Rule keyword across official Cucumber implementations.

  • Java - Limited support in 5.0.0, full support coming soon (project)
  • JavaScript - Coming soon in 7.0.0 (pull request)
  • Ruby - Coming soon in 4.0.0
  • .NET - Since SpecFlow 3.1
  • Go - Not supported yet
@davidjgoss davidjgoss added 📖 documentation Improvements or additions to documentation 🧷 pinned Tells Stalebot not to close this issue labels Jan 21, 2020
@davidjgoss davidjgoss self-assigned this Jan 21, 2020
@davidjgoss
Copy link
Contributor Author

davidjgoss commented Jan 21, 2020

This issue can be linked from the docs (see cucumber/docs#440) and closed once all implementations have Rule support in their latest stable version.

I'm not exactly clear on the status/outlook for .NET and Go, maybe someone could update those?

@justindwyer6-archive
Copy link

Is there any update on Ruby support for this?

@luke-hill
Copy link
Contributor

@justindwyer6 - At the moment Cucumber4 was just released, primarily this changed a lot of auto-loading algorithm stuff and it also started to use the new formatters. That was always the plan for v4. It's likely this won't hit ruby in the short term, but it could hit at some point during the v4 life-cycle. I've been a bit out of the loop recently, but I will be getting back involved a lot more soon.

@p2635
Copy link

p2635 commented Oct 16, 2020

Any news on the .NET side?

@luke-hill
Copy link
Contributor

ping @SabotageAndi

@SabotageAndi
Copy link
Contributor

@p2635

It is there since SpecFlow 3.1:

https://specflow.org/blog/specflow-specflowrunner-3-1-are-here/
https://docs.specflow.org/projects/specflow/en/latest/Gherkin/Gherkin-Reference.html#rule

There are still limitations in the VS Extensions with it, but at runtime it is working.

@SabotageAndi
Copy link
Contributor

I adjusted the issue description

@p2635
Copy link

p2635 commented Oct 19, 2020

Thanks @SabotageAndi , how can I follow the updates with the syntax highlighting? I've subscribed to this issue so I hope that is enough.

@SabotageAndi
Copy link
Contributor

@p2635 No, subscribing to this issue will not be enough. Without @luke-hill ping, I would never notice this issue. The SpecFlow development happens in its own GitHub organization. We don't monitor the cucumber repositories. The best way to notice if there is an update to it is to follow us on Twitter or our Blog.

@p2635
Copy link

p2635 commented Oct 19, 2020

That's great @SabotageAndi , I'm already subscribed to the blog so it's all good.

@luke-hill
Copy link
Contributor

Given this is implemented in most other languages. And gherkin has for several versions had Rule working stably, I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📖 documentation Improvements or additions to documentation 🧷 pinned Tells Stalebot not to close this issue
Projects
None yet
Development

No branches or pull requests

5 participants