Integrate Gherkin3 Parser...

[marktaling]

The current Gherkin parser requires a lot of assemblies making the commandline tooling quite bulky.
I think we need to take a look at this .Net based parser

https://github.com/cucumber/gherkin3/tree/master/dotnet

[jmezach]

I've started work on this. From what I can tell so far it doesn't seem that big of a change and it would remove dependency on SpecFlow altogether. That should make #40 easier to do as well.

[jmezach]

I've finished the basics of moving over to the Gherkin3 parser, but I noticed that if a feature file has a #language comment at the top with a two part notation (ie. en-US or nl-NL) it throws an exception. Seems like only single part notation (ie. en or nl) is supported by the Gherkin parser.

Figuring that SpecFlow works just fine with the two part notation I had a look at how they implemented this. Looks like they try the two part first, and if that fails the strip the second part and try again: https://github.com/techtalk/SpecFlow/blob/master/TechTalk.SpecFlow.Parser/SpecFlowGherkinParser.cs#L15-L39

We could implement it the same way but we'll also have to figure out what to do with the --language option that the command line currently supports. Perhaps we should implement a GherkinDialectProvider that uses the command line option if supplied?