Repository navigation
fix: stop adding topic and retain when writing an MQTT lastWill - #47
Merged
Merged
Conversation
LastWill wrote `topic` with WriteRequiredProperty and `retain` from a
non-nullable bool, so reading `lastWill: { qos: 1 }` and writing it back
produced `topic:` (null) and `retain: false`. Both fields are optional in
the MQTT binding spec.
`retain` now has a nullable backing field (same pattern as
MQTTOperationBinding), and both fields are written only when set. The
public `Retain` property keeps its bool type, so this is not a breaking
API change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
VisualBean
approved these changes
Oct 17, 2026
bielu
marked this pull request as ready for review
October 17, 2026 17:32
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.
Problem
Reading an MQTT server binding with a partial
lastWilland writing it back changes the document:LastWill.SerializewrotetopicwithWriteRequiredProperty(so a missing topic becametopic: null) andretainfrom a non-nullablebool(so a missing value becameretain: false). Both fields are optional in the MQTT binding spec.Change
retainnow has a privatebool?backing field; the publicRetainproperty is stillbool(defaults tofalse), the same patternMQTTOperationBindingalready uses forqos/retain. No public API change.topicandretainare written withWriteOptionalProperty, so they appear only when set. An explicitly assignedRetain = falseis still written.Tests
Added to
MQTTBindingVariants_Should:LastWill_WithoutTopicAndRetain_RoundTripsWithoutAddingThem(V2 and V3): fails onvnext, passes with this change.LastWill_WithExplicitRetainFalse_WritesRetain: guards that an explicitfalseis still written.The existing
V2_MQTTServerBinding_FilledObject_SerializesAndDeserializesround-trip is unchanged, and the full suite passes on net8.0/net9.0/net10.0.🤖 Generated with Claude Code