The changes in the 1.0.0 release broke the tag filtering functionality so that an error is thrown if an entire feature file is filtered out (and not just some of the scenarios).
In that case an error like this will be encountered:
× When a report is generated with the code "new Generator().generate(this.allFeaturesPath, null, '@cats')" # features\support\generationSteps.js:54
TypeError: Cannot read property 'featureId' of undefined
at C:\git\cucumber-forge-report-generator\src\Generator.js:267:28
at Array.forEach (<anonymous>)
at getFeatureButtons (C:\git\cucumber-forge-report-generator\src\Generator.js:264:6)
at getDirectoryButtonHtml (C:\git\cucumber-forge-report-generator\src\Generator.js:287:21)
at C:\git\cucumber-forge-report-generator\src\Generator.js:304:66
at Array.forEach (<anonymous>)
at getSidenavButtonsHtml (C:\git\cucumber-forge-report-generator\src\Generator.js:304:30)
at create (C:\git\cucumber-forge-report-generator\src\Generator.js:324:25)
at Generator.generate (C:\git\cucumber-forge-report-generator\src\Generator.js:372:12)
at eval (eval at <anonymous> (C:\git\cucumber-forge-report-generator\features\support\generationSteps.js:57:20), <anonymous>:1:17)
at CustomWorld.<anonymous> (C:\git\cucumber-forge-report-generator\features\support\generationSteps.js:57:20)
The changes in the 1.0.0 release broke the tag filtering functionality so that an error is thrown if an entire feature file is filtered out (and not just some of the scenarios).
In that case an error like this will be encountered: