Require type label on custmsg BaseMessage emissions - #2222
Draft
pkcll wants to merge 1 commit into
Draft
Conversation
Add WithType and WithLabelsAndType to MessageEmitter, validate LabelKeyType at emit time, and update wasm host mocks for the new interface methods.
5 tasks
Contributor
|
Contributor
|
This PR is stale because it has been open 30 days with no activity. |
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.
Summary
LabelKeyType("type") andWithType/WithLabelsAndTypehelpers on the custmsg labeler APIEmitnow returns an error when thetypelabel is missing from BaseMessage labelsDownstream consumers can distinguish NodeConfig, Heartbeat, workflow logs, and other BaseMessage emissions without parsing payload content.
Test plan
go test ./pkg/custmsg/...go test ./pkg/workflows/wasm/host/...Made with Cursor