Changes in `[filepart]` and `[filepath]`

Current behavior

I am unable to use the [filepart] or [filepath] placeholders to use step definitions when the test and step definition folders are alongside eachother.

Desired behavior

Ideally either [filepart] would function as it did previously, or a new option would be added that functions like v10, returning:

• The name of the feature file, minus the extention.
• The folder above the feature file + the feature file name.

For example, given the test cypress/tests/smoke/smoke.feature, [filepart] would yield:

['smoke', 'smoke/smoke']

Test code to reproduce

More details about the issue, and before/after examples can be found on my Test Repo.

Versions

• Cypress version: 10.2.0
• Preprocessor version: 11.3.0
• Node version: v16.15.1

Checklist

• I’ve read the FAQ.
• I’ve read Instructions for logging issues.
• I’m not using cypress-cucumber-preprocessor@4.3.1 (package name has changed and it is no longer the most recent version, see #689).

[badeball]

This has been released as v12.0.0.

[badeball]

That would blow up the directory with step definitions for large projects and cause ambiguity issues for colliding file names. Basically a pretty big step back and not something I’m considering.

What I’ve pretty much settled on in my mind, is to compile the common ancestor paths shared between all spec files and use that as an implicit integration folder, similar to what Cypress already does with some of their stuff. This would revert the changes required when having upgraded to v11.0.0 of the preprocessor, still support everything as before, and allow users to put their hierarchy of step definitions beside the integration folder.