Skip to content

GH-5360 scaffold: don't plan every emitted event as an Apply on every stream - #5374

Merged
jeremydmiller merged 1 commit into
mainfrom
stoat/nov-5-releases/wv-5360
Nov 5, 2026
Merged

jeremydmiller merged 1 commit into
mainfrom
stoat/nov-5-releases/wv-5360

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Part of #5360.

When a slice has .Against<A>() and .StartsStream<B>(), Emits<T>() carries no stream, so the scaffold planned every event as an Apply on both A and B. It now plans none for such a slice and adds a warning notice (new code emitted-event-stream-ambiguous) naming the streams.

Done: option 3 from the issue (notice instead of a plan). Left: option 1 (a lane on the emit, .Emits<T>().On<Account>()) needs a JasperFx.Events change; option 2 (infer from existing Apply/Create). Slices that only use several Against<> keep their current behaviour (GH-4895 tests rely on it).

🤖 Generated with Claude Code

…st one stream and starts another

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@jeremydmiller

Copy link
Copy Markdown
Member Author

Ran: dotnet test --project src/Testing/CoreTests -f net9.0 --filter-class "*event_model_scaffold*" — 66 passed, 0 failed (includes the new test). The Http scaffold test project printed no results, so it was not verified.

@jeremydmiller
jeremydmiller merged commit ec72177 into main Nov 5, 2026
This was referenced Nov 6, 2026
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