Skip to content

refactor(project): Name one run of a step an invocation - #1654

Merged
matz3 merged 2 commits into
mainfrom
refactor/invocation-terminology
Oct 14, 2026
Merged

matz3 merged 2 commits into
mainfrom
refactor/invocation-terminology

Conversation

@matz3

@matz3 matz3 commented Oct 12, 2026

Copy link
Copy Markdown
Member

Give one execution of a step a consistent name. A map step (keys/each) has one invocation per key; a scalar step (run) has exactly one invocation. The term pairs with the existing invocationData the StepRunner persists per key.

Replace the previous mixed use of "unit" in StepRunner, the build cache, and the related tests, docs, and skill notes. Rename the internal callback parameter unitCtx to invocationCtx. Keep "unit" where it means something else: "unit test", "unit of caching", a module path, or a measurement unit.

JIRA: CPOUI5FOUNDATION-1388

Give one execution of a step a consistent name. A map step (keys/each)
has one invocation per key; a scalar step (run) has exactly one
invocation. The term pairs with the existing invocationData the
StepRunner persists per key.

Replace the previous mixed use of "unit" in StepRunner, the build cache,
and the related tests, docs, and skill notes. Rename the internal
callback parameter unitCtx to invocationCtx. Keep "unit" where it means
something else: "unit test", "unit of caching", a module path, or a
measurement unit.

JIRA: CPOUI5FOUNDATION-1388
@matz3
matz3 requested a review from a team October 12, 2026 12:26
matz3 added a commit that referenced this pull request Oct 12, 2026
Apply the terminology from #1654 to the
incremental-build RFC.
Replace the mixed use of "unit" for one run of a step with
"invocation" in the step-based-task sections. Keep "unit" where it
means the unit of caching.

JIRA: CPOUI5FOUNDATION-1388
RandomByte
RandomByte previously approved these changes Oct 12, 2026
codeworrior
codeworrior previously approved these changes Oct 13, 2026

@codeworrior codeworrior left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread .claude/skills/incremental-build/architecture.md
Comment thread packages/project/lib/build/helpers/StepRunner.js Outdated
Rename the step-grained internals that actually operate on the
per-key grain to use the invocation name. A recorder is created once
per invocation, the per-key worker runs once per invocation, and the
selection method filters per-key entries, so none of them are
step-grained:

- StepRecorder -> InvocationRecorder, stepIndex -> invocationIndex
- the per-key worker arrow function runStep -> runInvocation
- the private method #selectStepsToRun -> #selectInvocationsToRun

The step-grained names stay: the public runSteps method and the
@ui5/builder runSteps task helper, #computeStepReturnSignature which
folds every key into one step signature, and #notifyStepExecution
with the anyStepExecuted / notifyStepExecution boundary names. A step
is the authored unit, an invocation is one run of it.
@matz3
matz3 dismissed stale reviews from codeworrior and RandomByte via b77a9fa October 14, 2026 07:31

@codeworrior codeworrior left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@matz3
matz3 merged commit 6fcc8ec into main Oct 14, 2026
77 checks passed
@matz3
matz3 deleted the refactor/invocation-terminology branch October 14, 2026 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants