Leading Tab characters break parser logic #512
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Leading Tab characters is kept in the trimmed_line and
GherkinLine_start_with can't recognize keywords in this case
Summary
If a feature file uses Tab character for indentation then the parser build incorrect AST: nothing keywords will not be detected in the text with indentation.
Details
I'v modified GherkinLine_new to remove leading Tab characters in the trimmed_line field as well as whitespaces.
Motivation and Context
Our editor allows to use Tab characters. In this case we had invalid AST.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: