This repository has been archived by the owner on Mar 19, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
invalidParameters does not work in tests #566
Labels
Comments
This looks like it's calling You say it's |
Just tried on rug-rugs, and I see the above error. |
kipz
added a commit
that referenced
this issue
May 5, 2017
kipz
added a commit
that referenced
this issue
May 5, 2017
This is due to how step names can override one another, and 'parameters are invalid' from handlers overrode the one from project (which has a different signature). So the wrong JS was called, and hence invalidParameters was called on the wrong object. |
Closed by #568 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Gherkin well-known step "parameters were invalid" no longer seems to work for projects. It's TypeScript implementation relies on the ScenarioWorld.invalidParameters method. When it is run against a build of the current master branch, you see:
@kipz thought this might be related to some filtering he implemented in #565.
The text was updated successfully, but these errors were encountered: