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

Generate a feature file from a parsed document (de-parse effectively) #4

Closed
pligor opened this issue Nov 4, 2022 · 1 comment
Closed

Comments

@pligor
Copy link

pligor commented Nov 4, 2022

🤔 What's the problem you're trying to solve?

As one has the Parser like here:

parser = Parser()
gherkin_document = parser.parse("Feature: ...")

and has changed/updated a few elements of the gherkin_document (which is really just a dictionary in Python)
Isn't it logical for many instances to want to re-generate the feature file ?

✨ What's your proposed solution?

A script which extracts the information from within the Parsed Gherkin document and generates a valid .feature file with this feature

⛏ Have you considered any alternatives or workarounds?

If there is not none already the only way to go is to build one myself but for this community it would be a more mature solution if you could integrate it in this repo

📚 Any additional context?


This text was originally generated from a template, then edited by hand. You can modify the template here.

@mpkorstanje
Copy link
Contributor

Duplicate of cucumber/gherkin-utils#3

I'm currently in the process of extracting Gherkin from the common repo. This repo exists but it's still a work in progress. Once the work is done, I'll migrate the issues related to Gherkin as well.

Sorry about the ambiguity.

@mpkorstanje mpkorstanje closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2022
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

2 participants