cucumber-expressions: generated expressions - expose argument names

[charlierudolph]

@aslakhellesoy

resolves #82
I think cucumber-expressions needs it own repo similar to gherkin so there is a single CI build to test everything.

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[aslakhellesoy]

I think cucumber-expressions needs it own repo similar to gherkin so there is a single CI build to test everything.

We'll be gradually moving the entire Cucumber ecosystem into a single monorepo (this one), and have read-only manyrepos, one for each language. The cucumber-expressions library already has manyrepos:

• https://github.com/cucumber/cucumber-expressions-java
• https://github.com/cucumber/cucumber-expressions-javascript
• https://github.com/cucumber/cucumber-expressions-ruby

This is currently synced manually by me using a script called push-subtrees. I want to automate this as part of CI, but haven't gotten around to it yet. FYI this script uses a tool called splitsh-lite

[charlierudolph]

K. My main concern was when I create a PR here, I'd like a CI build for each of the subtrees I touch.

[aslakhellesoy]

Yes I would love for that to happen, but it's tricky to set up.

[aslakhellesoy]

@charlierudolph I've requested some help with this in splitsh/lite#24

[charlierudolph]

awesome!

[lock]

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.