Establish relative record name convention (fix #12) #28
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
emersion
added a commit
to emersion/libdns-digitalocean
that referenced
this pull request
Jul 28, 2023
…ecord names" This reverts commit bac007b. In [libdns#28], it was decided to use relative names in Record.Name. [libdns#28]: libdns/libdns#28
mholt
pushed a commit
to libdns/digitalocean
that referenced
this pull request
Jul 28, 2023
…ecord names" (#9) This reverts commit bac007b. In [libdns#28], it was decided to use relative names in Record.Name. [libdns#28]: libdns/libdns#28
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.
Clarify that record names are relative to their zone. Improve documentation, add helper functions and tests, and write examples.
Should close #12, hopefully to satisfaction.