Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Roslyn code-analysis #122

Open
paulturner-pg opened this issue Jun 18, 2023 · 0 comments
Open

Support Roslyn code-analysis #122

paulturner-pg opened this issue Jun 18, 2023 · 0 comments

Comments

@paulturner-pg
Copy link

🤔 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant