Skip to content
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

[chore] rosetta-specifications@v1.4.9 #271

Merged
merged 4 commits into from
Dec 8, 2020
Merged

Conversation

patrick-ogrady
Copy link
Contributor

@patrick-ogrady patrick-ogrady commented Dec 8, 2020

This PR updates rosetta-sdk-go to the latest release of rosetta-specifications. This is a pretty minor release compared to other recent releases.

Changelog

  • Assert SyncStatus
  • Assert SearchTransactionsResponse.TotalCount

rosetta-specifications Changelog

  • Return Synced Status #71
  • [indexer] Add total_count field #70

@@ -78,6 +78,27 @@ func Version(version *types.Version) error {
return nil
}

// SyncStatus ensures any types.SyncStatus is valid.
func SyncStatus(status *types.SyncStatus) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this always returns error (or nil), I'd prefer a name like SyncStatusError or ValidateSyncStatus. What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is consistent with all other functions in asserter. Currently, the pattern is that the name of the asserter method is the name of the struct it is asserting.

If we want to migrate to your naming strategy, I'd recommend we do that in a separate PR.

@patrick-ogrady patrick-ogrady merged commit cebc77f into master Dec 8, 2020
@patrick-ogrady patrick-ogrady deleted the patrick/v1.4.9-spec branch December 8, 2020 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants