Repository navigation
Resolve complete relation tuples for generated change propagation - #194
Merged
Merged
Conversation
This was referenced Oct 22, 2026
first-assist
force-pushed
the
platform/composite-readonly-changed-r6
branch
2 times, most recently
from
October 23, 2026 18:23
59760ee to
8649b99
Compare
added 4 commits
October 24, 2026 06:37
first-assist
force-pushed
the
platform/composite-readonly-changed-r6
branch
from
October 23, 2026 19:38
d6ab6d2 to
163aeb0
Compare
first-assist
marked this pull request as ready for review
October 23, 2026 20:35
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.
Resolve generated upward propagation through every declared relation from/to component, then reauthorize the complete source/target tuple and canonical target key before release. Bound fanout to the remaining event budget and roll back overflow. Direct events seed cycle detection with the typed target identity and origin. Tests cover alternate provider IDs, colliding tuples, revocation, rollback and moved edges. This focused prerequisite does not finish #191, #184 or draft #189.
Rebased onto merged #193 main
f2be662ae795085e4712339c02b3f94ddaa55f05. ORM/macros advance together to 0.63.0. Root-relayed ORM job120591252153foundclippy::enum_variant_nameson generated aggregate field enums whose fields all end inId. The macro now permits that lint only on its generated enum; other lints remain enforced. Earlier root-relayed formatter job120583423632supplied 31 exact layout hunks, applied source-only with old-context matching.Source-only checks: documentation 210, generated inventory, package release policy against #193, diff check and all seven lockfile external identities pass. No local Cargo, Rust, formatter, test or backend command ran. Fresh exact-head hosted CI and issue acceptance remain pending. Keep draft; GentleCarp alone merges.
Current source:
163aeb0f8ffd34259841e2b88dbfc8c96be804f4(tree8c5c65ab08ba4680b6f6958408aad0d65e04619d).Documentation impact