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

gcs: update error types. #2262

Merged
merged 1 commit into from
Nov 11, 2020
Merged

Conversation

dnldd
Copy link
Member

@dnldd dnldd commented Jul 15, 2020

depends on #2463

This updates the gcs error types to leverage go 1.13 errors.Is/As functionality as well as confirm to the error infrastructure best practices outlined in #2181.

@davecgh davecgh added this to the 1.7.0 milestone Jul 15, 2020
Copy link
Member

@davecgh davecgh left a comment

Choose a reason for hiding this comment

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

This is changing the public API in a non-backwards compatible way. That means a major module version bump is required. Please follow the standard practice for a major version bump to v3. It should probably be in a separate PR, but at the very least a separate commit before these changes are made.

@davecgh
Copy link
Member

davecgh commented Nov 11, 2020

Needs rebase and to bump the gcs module required version to go 1.13.

Copy link
Member

@davecgh davecgh left a comment

Choose a reason for hiding this comment

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

Looks good overall. Just a few inline comments and the aforementioned need to rebase and update the required Go version in the go.mod.

gcs/error.go Outdated Show resolved Hide resolved
gcs/error.go Show resolved Hide resolved
gcs/error_test.go Outdated Show resolved Hide resolved
This updates the gcs error types to leverage go 1.13 errors.Is/As functionality as well as confirm to the error infrastructure best practices.
@davecgh davecgh merged commit e092918 into decred:master Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants