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

Sub-flows features #74

Open
info-rchitect opened this issue Jan 15, 2020 · 1 comment
Open

Sub-flows features #74

info-rchitect opened this issue Jan 15, 2020 · 1 comment
Labels
feature discussion Discussion on a feature's requirements or implementation

Comments

@info-rchitect
Copy link
Member

Hi,

This is an issue regarding sub-flows features. Here are a couple items that have come up:

  1. Should we continue to reload the target by default as in O1?
  2. When a sub-flow is imported multiple times, users would like to be able to name the generated groups using options

Feel free to add on.

@info-rchitect info-rchitect added the feature discussion Discussion on a feature's requirements or implementation label Jan 15, 2020
@redxeth
Copy link
Member

redxeth commented Jan 15, 2020

Good idea-- also some additional features that we have needed at various times in O1 related to sub-flows (maybe we're not meaning the same kinds of sub-flows-- but will throw this out there):

  • Easy way to get pattern name in the flow itself
  • Easy way to get flow or sub-flow file name in flow itself-- this would be handy so when later looking at a generated test flow you can FIND where the test was defined, esp if you have a complex flow/sub-flow structure.
  • For a sub-flow to access the flow (or other sub-flow) calling it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature discussion Discussion on a feature's requirements or implementation
Projects
None yet
Development

No branches or pull requests

2 participants