✨Draft parsing of SRV records in r_nsl()✨
#48
+32
−0
Conversation
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.
First pass at implementing parsing of SRV records - returns them as a space separated character string.
✨ Majority of this code was generated via claude code ✨ - I've reviewed what is generated and everything looks reasonable to me in terms of implementation, matching existing code, and output.
Tested on MacOS and a Windows vm - results again look reasonable but do differ (windows returns multiple lines). Given this discrepancy I've opted for a very minimalistic test based on the original issue. This likely needs revision but there were not other
nsl()tests yet to crib from.