[Core] Add more details to ParserException

[zutshiy]

Summary

Adding the path to the resource for easier investigation during parsing exceptions in cucumber.

Details

Added resource path to the exception thrown under FeatureParser.parseResource() method to allow user to see which file failed to parse.

Motivation and Context

Better user experience. It is useful to know which file caused the parser exception. Refer slack conversation

Nicolas [Mar 30th at 3:03 AM]
Hello! I'm starting off with cucumber-jvm and I've noticed that the Parser errors don't specify which .feature file is broken. Is there any way to enable this behavior? We're looking at adding multiple feature files at a time in a medium sized QA team and this would help out quite a bit. Thanks!

mpkorstanje [8 days ago]
And if you're willing to invest a little time you could probably submit a patch too:

You'd have to add some details around here I think:

core/src/main/java/cucumber/runtime/model/FeatureParser.java:40
throw new CucumberException(e);

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[coveralls]

Coverage remained the same at 86.184% when pulling 15eda70 on gazler22:featureparser-patch into 0caf37c on cucumber:master.

[mpkorstanje]

Looks good!

[mpkorstanje]

Cheers!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.