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 28, 2019. It is now read-only.
Feature: lexing error from octothorpe
# foo
You will get a LexingError on this line
When I run cucumber test.feature
Then the output contains:
Lexing error on line 4: ' You will get a LexingError on this line'. See http://wiki.github.com/cucumber/gherkin/lexingerror for more information. (Gherkin::Lexer::LexingError)
I did notice in the aruba readme it mentions escaping some markdown/gherkin clashes, but I don't think this particular case should result in a LexingError. If it's legit to have some error (I'm not so certain it is), it should be on the line with the octothorp. TBH I'm not sure aruba's escaping advice is valid, but figured I'd mention it since it specifically called out the gherkin does something with # lines.
Given a file named
test.feature
with:When I run
cucumber test.feature
Then the output contains:
I did notice in the aruba readme it mentions escaping some markdown/gherkin clashes, but I don't think this particular case should result in a LexingError. If it's legit to have some error (I'm not so certain it is), it should be on the line with the octothorp. TBH I'm not sure aruba's escaping advice is valid, but figured I'd mention it since it specifically called out the gherkin does something with
#
lines.Oh, and this was with:
The text was updated successfully, but these errors were encountered: