-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement checkZoneDistribution #64
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On hold until dnsimple/dnsimple-developer#153 is approved and merged.
Documentation is live. I updated code with consistent naming, and updated the fixtures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have both checkZoneDistribution
and checkZoneRecordDistribution
in the same PR.
I implemented both the features, as requested
import "fmt" | ||
|
||
// ZoneDistribution is the result of the zone distribution check. | ||
type ZoneDistribution struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you feel about renaming this struct into DistributionResult
, and having both zoneDistributionResponse and zoneRecordDistributionResponse to use the same struct?
We don't pay for structs, but I hardly see the reason ATM to use 2 different types. It may makes things harder on the consumer side (especially given they are not an interface, and Go is strictly typed).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intentionally didn't declared an unified type because it looked like premature DRY.
On the other hand, we unify a lot of responses of the same type. Eg. registrar and domain services use domainResponse
. So I think we can unify this as well.
No description provided.