Conversation
3 tasks
Pass optional readonly module identity through the existing reverse transform options in both remote reconstruction and local deploy comparison. Specifications can use envelope identity without adding feature-specific branches to generic callers. Keep this framework capability independent of Events adoption. A synthetic specification verifies both identity sources and unchanged config output; existing transforms do not need to consume the new context.
dpeacock
force-pushed
the
dp-module-transform-context
branch
from
September 25, 2026 16:53
935bbd0 to
54e984d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WHY are these changes introduced?
When the CLI converts a module's configuration back to local app config, the configuration alone may not contain the module's identity. Today the transform receives flags, but not the module handle that both callers already know.
WHAT is this pull request doing?
Pass an optional, readonly module handle to reverse configuration transforms from both places that call them:
Existing transforms can ignore the new context, so this does not change current module behavior. It provides a small shared capability that module-specific code can adopt without adding special cases to generic callers.
This PR contains no Events-specific behavior and does not change payload schemas or make additional requests.
Validation
A synthetic configuration module verifies that both callers receive the correct handle and continue producing an unchanged config. The full app suite, package type-check, and lint pass.
No changeset is included because this is an internal framework capability with no user-facing behavior on its own.
Checklist