Skip to content

spec(glue): cross-model schedule source (schedules[].model + forEach.model) - #5

Open
delchev wants to merge 1 commit into
mainfrom
spec/cross-model-schedule-source
Open

spec(glue): cross-model schedule source (schedules[].model + forEach.model)#5
delchev wants to merge 1 commit into
mainfrom
spec/cross-model-schedule-source

Conversation

@delchev

@delchev delchev commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Documents a schedule whose source entity (and optionally a forEach collection) lives in another model, referenced by model: <uses alias>. This lets a schedule live with the module that owns the CREATED rows instead of being forced into the source's module.

  • Generate action only. A cross-model source with notify is rejected — notify needs the source's relation metadata, which only a local entity carries.
  • Read-only source. A schedule never writes its source.
  • Validation split (mirrors relations): the model: alias must be a declared uses: (checked at parse); the source entity and every where/map/match field reference are checked at generation against the owner model — an unresolvable owner or a mistyped field drops that schedule with a warning, never emitting code that cannot compile.

Removes the corresponding 'Planned — not yet implemented' entry.

Leaving this open for the maintainer to review/merge.

…model)

A schedule's source entity - and a forEach collection - may live in another
model via model: <uses alias>, so a schedule can live with the module that owns
the created rows. Generate action only; the source is read-only. Validation
splits like relations: alias-declared at parse, field references at generation.
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.

1 participant