GitHub user sshiv012 added a comment to the discussion: Discuss workflow macro design and lifecycle
I support treating macros as reusable subgraphs with explicit ports and independently pinned versions. [KNIME components](https://docs.knime.com/ap/latest/analytics_platform_components_guide/) (I believe this was considered as an inspiration) provide a useful precedent for separating local grouping from shared components and adopting updates explicitly. I think having the below might be nice, - Allow macros to be tested with sample inputs, even if only workflows are independently executable - Keep defaults in the definition and overrides in each instance; expose nested properties explicitly. - Frontend expansion seems reasonable initially, but preserve the hierarchy mapping for errors and statistics, and maybe leave a path towards server-side expansion? GitHub link: https://github.com/apache/texera/discussions/5248#discussioncomment-18806035 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
