You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Currently, when the user selects a directory, CFD will crawl through all sub-directories looking for *.feature files. This can cause problems. For example, if a Node project has a dependency that includes feature files those feature files can show up in the node_modules folder. Then, if someone uses CFD to generate a report for the original Node project, CFD will also include the features from the dependency in the generated report.
There is probably a list of directories (including node_modules) that we could hard-code and ignore.
An alternative option would be to try and parse SCM metadata (e.g. the .gitignore file) and just ignore what it ignores....
The text was updated successfully, but these errors were encountered:
Now that the generator, itself, is responsible for loading the feature files from the directories, it seems like this issue belongs here and not in cucumber-forge-desktop.
It is also worth noting that #41 has already implemented the first part of this issue by excluding feature files from the target and node_modules directories. I am leaving this issue open in case we ever decide to make the generator "git aware" and ignore based on something like the .gitignore file.
Currently, when the user selects a directory, CFD will crawl through all sub-directories looking for
*.feature
files. This can cause problems. For example, if a Node project has a dependency that includes feature files those feature files can show up in the node_modules folder. Then, if someone uses CFD to generate a report for the original Node project, CFD will also include the features from the dependency in the generated report.There is probably a list of directories (including node_modules) that we could hard-code and ignore.
An alternative option would be to try and parse SCM metadata (e.g. the .gitignore file) and just ignore what it ignores....
The text was updated successfully, but these errors were encountered: