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 renaming steps in feature file #63

Open
aurnoi1 opened this issue Jan 24, 2020 · 4 comments
Open

Support renaming steps in feature file #63

aurnoi1 opened this issue Jan 24, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@aurnoi1
Copy link

aurnoi1 commented Jan 24, 2020

Deveroom version: 1.5.1
Visual Studio 2019 version: 16.4.3

One of the feature of Specflow Extension for VS is the ability to rename steps from the feature file. Since these steps are made to be reused, it is a real pain to do it manually. Unless I am mistaking this feature is not present in deveroom.

Is it plan in the road map?

@gasparnagy gasparnagy added the enhancement New feature or request label Jan 27, 2020
@gasparnagy
Copy link
Contributor

This is definitely a feature that we would like to support. I don't have a very concrete plan for it, because this would require a little bit of research on how we can connect to the roslyn code engine. But I hope to have this soon.

@pmashurenko
Copy link

If you're going to implement this, please think about possibility to have such feature implemented in a way that it would understand regular expressions that might be used in Given/When/Then attributes and won't break them during rename.

@alexandermikuta
Copy link

It seems renaming is still not possible. Any news or plans about this? This feature would be really helpful.

@gasparnagy
Copy link
Contributor

@alexandermikuta we have some plans together with the SpecFlow team to get that in, but it is not done yet.

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

No branches or pull requests

4 participants