add path and line number to stepdefs.json #214
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An option --dotcucumber is so nice that I, as a programmer, am encouraged to write more and more well understandable steps.Since I have many steps, I've wanted to glance an index, copy them to feature, and step into the definition.
So is it good to include step definition's path to
stepdefs.json
?An use case of this is: https://github.com/moro/unite-stepdefs -- a vim plugin using this file:column output.
thanks.