Cloudflare: Fix parsing of priority field in record (fixes #367)#368
Merged
captncraig merged 1 commit intoStackExchange:masterfrom Jun 22, 2018
pgaskin:fix-cloudflare-priority
Merged
Cloudflare: Fix parsing of priority field in record (fixes #367)#368captncraig merged 1 commit intoStackExchange:masterfrom pgaskin:fix-cloudflare-priority
captncraig merged 1 commit intoStackExchange:masterfrom
pgaskin:fix-cloudflare-priority
Conversation
Contributor
|
I can't figure out why gogen is failing. Hey, @captncraig, could you take a look? |
Collaborator
Author
|
Any news? |
rblenkinsopp
pushed a commit
to rblenkinsopp/dnscontrol
that referenced
this pull request
Aug 21, 2020
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
4 participants
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.
This fixes #367 by making
cfRecorduse ajson.Number(to allow numbers to be parsed from strings) when parsing the Cloudflare API response.