Is your feature request related to a problem? Please describe.
When authoring feature files with Behave VSC:
- Steps that are local code show up colorized as functional, and auto-complete works as expected.
- When Steps come from a dependency library, unable to reuse same functionality after several attempts and approaches to import them.
Describe the solution you'd like
If a python behave project has dependencies, and in the features/steps/ folder a file may be added such as:
# shared_steps.py
# from shared_behave_steps import *
import shared_behave_steps.steps.functional_group1
import shared_behave_steps.steps.functional_group2
import shared_behave_steps.steps.functional_group3
Describe alternatives you've considered
If this functionality already exists, potentially a more expansive q&a/troubleshooting guide. If this functionality does not exist, options around how to enable it in order to allow reuse of behave step libraries rather than copying code across projects.
Additional context
Last tested on behave vsc pre-release 0.6.4
Is your feature request related to a problem? Please describe.
When authoring feature files with Behave VSC:
Describe the solution you'd like
If a python behave project has dependencies, and in the features/steps/ folder a file may be added such as:
Describe alternatives you've considered
If this functionality already exists, potentially a more expansive q&a/troubleshooting guide. If this functionality does not exist, options around how to enable it in order to allow reuse of behave step libraries rather than copying code across projects.
Additional context
Last tested on behave vsc pre-release 0.6.4