-
-
Notifications
You must be signed in to change notification settings - Fork 45
fix: createBucket pass through all values returned by backend #89
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
Conversation
instead of cherry picking only name - we still do this in the types though. also ensures data is always an object. Fixes #6
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.
lgtm!
At this stage why are we cherry-picking in just the types and not having them match the actual return object?
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.
Ah looks like there's a test that isn't passing
The backend is only returning the name of the new bucket and not the entire Bucket object. If backend returns the full object, we could have just had the return type as Fixed tests! |
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.
Makes sense! Pick
is a great option then
🎉 This PR is included in version 1.8.0-next.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.0.0-rc.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
instead of cherry picking only name - we still do this in the types though.
also ensures data is always an object.
Fixes #6