Skip to content
This repository has been archived by the owner on May 28, 2019. It is now read-only.

LexingError on the line following a line starting with an octothorp #221

Open
soulcutter opened this issue Jan 2, 2013 · 0 comments
Open

Comments

@soulcutter
Copy link

Given a file named test.feature with:

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.

Oh, and this was with:

*** LOCAL GEMS ***

builder (3.1.4)
bundler (1.2.1)
cucumber (1.2.1)
diff-lcs (1.1.3)
gherkin (2.11.5)
json (1.7.6)
rake (0.9.2.2)
rubygems-bundler (1.1.0)
rvm (1.11.3.5)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant