Repository navigation
Conversation
INTER-2457. Regenerated Event as a oneOf wrapper to show the compile break. Do not merge.
|
|
Following files do not match corresponding templates: To fix this warning, make sure template files are up-to-date, and generate files by running the following command: bash ./generate.sh |
Wrong commit message format detectedWe use Semantic Commit Messages in our project.
Run the next command in the project root to activate local hooks: sh ./install_hooks.shMore info you can find in job logs Commitlint ErrorsCommit: 7f58569 `chore: SPIKE Event oneOf discriminated union INTER-2457. Regenerated Event as a oneOf wrapper to show the compile break. Do not merge.`
|
pnpm exec changesetto create a changeset. |
|
This was a prototype done as part of a spike. Closing now, still usable as a reference during the production implementation. |
EventoneOf wrapper (EventDevice|EventEdge).sourcenow deserializes asEventDeviceand hydratessourcetodevice.source: edgeis unchanged.Compare with option C: #201
Do not merge.
Discussion point: omit vs flatten
Option B keeps the generated union. Callers must branch on
EventDevice/EventEdge. Option C flattensEventso existingevent.Identificationcall sites still compile.Known issue: CI will fail
Existing API tests still read flat
Eventfields (EventId,Identification, …) and do not compile. That is the spike.