Skip to content

Fix CloudEvents fallback and message aliases - #2453

Merged
jeremydmiller merged 1 commit into
JasperFx:mainfrom
lahma:default-cloud-event-type
Apr 8, 2026
Merged

jeremydmiller merged 1 commit into
JasperFx:mainfrom
lahma:default-cloud-event-type

Conversation

@lahma

@lahma lahma commented Apr 8, 2026

Copy link
Copy Markdown
Contributor
  • CloudEventsMapper now falls back to the original Envelope.MessageType when the raw CloudEvent alias is unknown, while still preserving the raw type for true dead-letter cases
  • HandlerGraph.RegisterMessageType(Type, string) now keeps multiple aliases for the same message type instead of silently dropping later aliases

@lahma
lahma marked this pull request as ready for review April 8, 2026 12:50
@lahma
lahma marked this pull request as draft April 8, 2026 12:54
* CloudEventsMapper now falls back to the original Envelope.MessageType when the raw CloudEvent alias is unknown, while still preserving the raw type for true dead-letter cases
* HandlerGraph.RegisterMessageType(Type, string) now keeps multiple aliases for the same message type instead of silently dropping later aliases
@lahma
lahma force-pushed the default-cloud-event-type branch from 6c8096c to af152ac Compare April 8, 2026 13:28
@lahma
lahma marked this pull request as ready for review April 8, 2026 13:30
@jeremydmiller
jeremydmiller merged commit 306a02b into JasperFx:main Apr 8, 2026
17 of 19 checks passed
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.

2 participants