feat(mdns): support null value for boolean txt records #822
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.
Description
This PR adds support for NULL values to be used in mdns txt records in order to differentiate "myKey" and "myKey=" txt records.
These two records are considered to be different in RFC 6763 Section 6.4, so it is important for us to have a way to handle them differently.
Previous usage (if NULL is not supported):
"myKey" -> key = "myKey", value = ""; "myKey=" -> key = "myKey", value = ""
Suggested changes:
"myKey" -> key = "myKey", value = NULL; "myKey=" -> key = "myKey", value = ""
Related
Testing
Checklist
Before submitting a Pull Request, please ensure the following: