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
I'd like to be able to use the Gherkin parser within the .NET code-analysis and code-generators ecosystem.
✨ What's your proposed solution?
An implementation of a parser which returned a syntax tree deriving from Microsoft.SyntaxNode would enable integration, allowing the components to treat Gherkin as a first-class language.
⛏ Have you considered any alternatives or workarounds?
At present, implementing an adapter between the output of the existing parser and a new syntax tree is possible, but would come with a performance cost and would never be able to take advantage of the incremental parsing system.
📚 Any additional context?
Whilst looking at building a code-generator for executing Gherkin-based scenarios, it became obvious that for .NET, the Roslyn analysers and code-generators are the way forward.
🤔 What's the problem you're trying to solve?
I'd like to be able to use the Gherkin parser within the .NET code-analysis and code-generators ecosystem.
✨ What's your proposed solution?
An implementation of a parser which returned a syntax tree deriving from
Microsoft.SyntaxNode
would enable integration, allowing the components to treat Gherkin as a first-class language.⛏ Have you considered any alternatives or workarounds?
At present, implementing an adapter between the output of the existing parser and a new syntax tree is possible, but would come with a performance cost and would never be able to take advantage of the incremental parsing system.
📚 Any additional context?
Whilst looking at building a code-generator for executing Gherkin-based scenarios, it became obvious that for .NET, the Roslyn analysers and code-generators are the way forward.
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: