invalidParameters does not work in tests

[ddgenome]

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:

<unknown>: Attempt to invoke method [invalidParameters] on type [TreeNode & Project]: Wrapping node named project-scenario-world; No exported method with that name: Found ArrayBuffer(addDirectory, addDirectoryAndIntermediates, addExecutableFile, addFile, backingArchiveProject, children, children, context, copyEditorBackingFileOrFail, copyEditorBackingFileOrFailToDestination, copyEditorBackingFilesOrFail, copyEditorBackingFilesPreservingPath, copyEditorBackingFilesWithNewRelativePath, copyEditorBackingProject, copyFile, copyFileOrFail, countFilesInDirectory, deleteDirectory, deleteFile, describeChange, directoryExists, editWith, fail, fileContains, fileCount, fileExists, fileHasContent, files, findFile, makeExecutable, merge, mergeTemplates, moveUnder, name, nodeName, nodeTags, nodeTags, nodeType, nodeType, pathTo, println, projects, regexpReplace, replace, replaceInPath, totalFileCount, value, value, value). Node tags are Set(Project)

@kipz thought this might be related to some filtering he implemented in #565.

[kipz]

This looks like it's calling ScenarioWorld.invalidParameters, rather than ProjectMutableView.

You say it's no longer seems to work for projects - can you elaborate on what that means? Do you have an example this failing somewhere?

[kipz]

Just tried on rug-rugs, and I see the above error.

[kipz]

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.

[ddgenome]

Closed by #568