'Examples' doesn't parse, but 'Examples:' does about gherkin2

[msassak]

I'm in favor of removing as many ambiguities from Gherkin the language as is reasonable, and in my opinion this is one of those cases. I don't think making it optional really adds anything, but Examples without a colon and with a description look awkward:

Examples all colors correct

vs.

Examples: all colors correct

Having said that, making the colon optional shouldn't be too hard if we want to avoid breaking features that have already been written.

[mattwynne]

The best would be if we could get a deprecation warning! Can you do that?

[msassak]

I think so. I'll look into it.

[msassak]

See http://github.com/msassak/cucumber/commit/044507c1aa7d00ff6e1525bec81d125cd81d4227

I added it to the Tree Walker in Cuke itself. I think it's best this way, as we can deprecate it now in preparation for Gherkin, and we don't need to fiddle with either of the parsers. I couldn't find a good way to provide more context e.g. "Examples group in /path/to/example.feature", but it's blaringly obvious when run with the pretty printer, so I think we should be OK.

[mattwynne]

Nice one. I think that's fine - I remember way back when it changed from 'Scenarios' to 'Examples' without warning and we just had to suck it up and fix all our features, so this is a great improvement on that.

[msassak]

This is a cucumber issue now: https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/500-deprecate-examples-keyword-without-a-colon, so I'm closing this ticket.