Add types to callback signatures of TypeScript implementations of the
Gherkin well-known steps for projects and handlers. This uncovered a
few errors, including:
The Scala implementation of ProjectScenarioWorld.modificationsMade()
returns a boolean, so changed its TypeScript interface to do the
same
The Scala implementation of
ProjectMutableView.copyEditorBackingProject() takes no arguments,
so changed its use in the Given step to not pass any
Using specific types for the world parameter was preferred to using
the more generic, e.g., CommandHandlerScenarioWorld was used
preferentially to ScenarioWorld where possible.
Consistent names for the project and world callback arguments.
Closes #574
Add copyright and license information.
Import from specific files rather than mode/Core.
Include step name in unimplemented error, see #570.
kipz
commented
7 years ago
Add types to callback signatures of TypeScript implementations of the Gherkin well-known steps for projects and handlers. This uncovered a few errors, including:
Using specific types for the world parameter was preferred to using the more generic, e.g., CommandHandlerScenarioWorld was used preferentially to ScenarioWorld where possible.
Consistent names for the project and world callback arguments.
Closes #574
Add copyright and license information.
Import from specific files rather than mode/Core.
Include step name in unimplemented error, see #570.