docs: phases - a moment an enrichment announces - #42
Open
delchev wants to merge 1 commit into
Open
Conversation
A value a listener computes after the insert must be written back without raising an update event, since an enrichment is not a user's edit. So it announced nothing at all, and a declarative consumer of that value had no moment to bind: bound to the create event it runs as a sibling of the enriching listener, with nothing ordering the two, and can produce a perfectly balanced journal entry for a null amount with every step green. Document the entity-level `phases:` declaration and the `onPhase` event axis: the generated data-access layer applies the enriched values and announces the phase in ONE write, so no consumer can observe one without the other. - spec/entities.md: the `phases` section. - spec/glue.md: the enrichment row in the event-axis table. - reference.md: the index rows.
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
1 participant
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.
The site half of intent-specification#57 (proposal 0028).
A value a listener computes after the insert must be written back without raising an update event, since an enrichment is not a user's edit. So it announced nothing at all, and a declarative consumer of that value had no moment to bind: bound to the create event it runs as a sibling of the enriching listener, with nothing ordering the two, and can produce a perfectly balanced journal entry for a null amount with every step green.
spec/entities.md- thephasessection: the declaration, the announce-in-one-write contract the generated data-access layer must satisfy, and the rules.spec/glue.md- the enrichment row in the event-axis table (now three axes).reference.md- the index rows forphases, the event axis andpostings.npm run docs:buildis clean.