-
Notifications
You must be signed in to change notification settings - Fork 254
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
Backwards incompatible changes for 4.0 #258
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #258 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 51 51
Lines 2198 2207 +9
=========================================
+ Hits 2198 2207 +9 ☔ View full report in Codecov by Sentry. |
41098e0
to
a4075ef
Compare
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.
The only thing here I see that I'm not keen on is the constructor panic. Looks great otherwise!
b6d17a0
to
3dd57f3
Compare
171c4b0
to
1d1f231
Compare
1d1f231
to
2c9c92e
Compare
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.
Looks like some changes to customer and order APIs were pulled in, are they related to the breaking changes?
I did some merging - rebasing after the recent PRs #260 and #261 and #259 which modified order.go and customer.go but I just looked at the diff here and it seems fine. Anything sticking out that shouldn't be there? |
Oh I was just looking at the diff between the pushes, but if that's just from the master branch then no worries. |
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.
Reapproving, as this latest change was only master rebases.
Couple of breaking changes that will go into 4.0
In particular, this one addresses PRs: