sub-flows ?

[moodymudskipper]

Not sure what would be the syntax, I think we'd be able to isolate some parts of the flow chart.

• One option could be to have special prefixes for comments to cut out the desired parts.

  ### This would be cut in a separate chart
  code
  ## a code chunk in this separate chart
  code
  ### another separate chart
  code
  # we finish a cut out chunk with either the start of a new one, or an empty comment if not
  ###

This won't allow nesting of such things (cutting out a chart that itself cuts out pieces), though it would be possible by having a standard prefix syntax or giving a vector of prefixes to the function, but we most probably don't need this level of sophistication.

• One other option is to have an additional option for the code, it can be shown, hidden, or split, and we'd end up with a bunch of diagrams, overall containing all the code, but not sure if it's practical

---

The reasoning behind this is that some pieces of code relative to specific features are hard to modularize, because they might use NSE, or use a lot of local variables, or need to be able to return directly. Our charts don't have this restriction though, so a feature could be isolated and charted as long as it's tagged properly.

This would be useful to discuss the logic of some operations in github issues for instance.

Note : to do this we need to support regular calls and not only functions!

[moodymudskipper]

can of woooooorms, on hold

[moodymudskipper]

done in a simpler way with subset arg

[github-actions[bot]]

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.