GitHub user carloea2 added a comment to the discussion: Discuss workflow macro 
design and lifecycle

@chenlica, the tracking issue is #8913 and the implementation is now available 
in draft PR #9541. The PR has conflicts with current `main`, so it is ready for 
design feedback while integration is pending.

One change since my October proposal addresses @parshimers’s point about where 
references are resolved. A workflow saves each macro’s revision, and the Scala 
compiler expands those pins when compiling the workflow. The saved hierarchy 
lets you open either of two usages of the same macro and see that occurrence’s 
errors and per-port statistics, including after reopening a run. We tested that 
with five usages of one revision at three depths.

For the lifecycle questions above, editing through a parent updates that 
occurrence’s path. Other usages keep their saved revisions. Form View exposes 
fields explicitly, with defaults in the definition and overrides on the 
instance. A workflow export carries the nested macro definitions and revisions.

Two questions where feedback would help: which external dependencies, such as 
files or UDF environments, should an import identify for the user? And for 
@sshiv012’s sample-input suggestion, would a small test workflow that calls the 
macro meet your needs, or is there a case where you need to test it directly 
from the macro editor?

GitHub link: 
https://github.com/apache/texera/discussions/5248#discussioncomment-19728818

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to