Repository navigation
fix: support plugin message contents without a transport - #430
Merged
Merged
Conversation
has_plugin_async_message_pact_between always starts a mock server for the plugin's transport, so content-only plugins such as avro can't be used. The plain message builder already drives a content plugin and hands the reified bytes to the test, but only for protobuf. Add MessageInteractionBuilder#with_plugin and #with_plugin_contents so any content plugin can be used on the message DSL, with specs for protobuf and avro (skipped when the avro plugin isn't installed). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
YOU54F
force-pushed
the
fix/plugin-message-without-transport
branch
from
October 21, 2026 13:45
ae05f6e to
0c9666a
Compare
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
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.
has_plugin_async_message_pact_between always starts a mock server for the plugin's transport, so content-only plugins such as avro can't be used. The plain message builder already drives a content plugin and hands the reified bytes to the test, but only for protobuf.
Add MessageInteractionBuilder#with_plugin and #with_plugin_contents so any content plugin can be used on the message DSL, with specs for protobuf and avro (skipped when the avro plugin isn't installed).