Right now the codebase only includes a single src/echodataflow/flows folder and all flow modules are in it. It seems would be a good thing if we allow another location for custom flows that do not ship with the package. This way it's a lot easier to add new flows in a place separate from the default flows.
One possibility is to allow users to specify an arbitrary location (absolute path) that flows can be read in. May need to work out the module import mechanism and have guardrails on duplicated names, etc.
Right now the codebase only includes a single
src/echodataflow/flowsfolder and all flow modules are in it. It seems would be a good thing if we allow another location for custom flows that do not ship with the package. This way it's a lot easier to add new flows in a place separate from the default flows.One possibility is to allow users to specify an arbitrary location (absolute path) that flows can be read in. May need to work out the module import mechanism and have guardrails on duplicated names, etc.