Skip to content

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

Merged
merged 2 commits into from
Aug 10, 2022

Conversation

inian
Copy link
Member

@inian inian commented Aug 10, 2022

instead of cherry picking only name - we still do this in the types though.

also ensures data is always an object.

Fixes #6

instead of cherry picking only name - we still do this in the types though.

also ensures data is always an object.

Fixes #6
@inian inian requested a review from alaister August 10, 2022 06:08
Copy link
Member

@alaister alaister left a 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?

Copy link
Member

@alaister alaister left a 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

@inian
Copy link
Member Author

inian commented Aug 10, 2022

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 Bucket. So I want the type check to fail if the user is accessing data.public for example. Is there a better of doing that?

Fixed tests!

Copy link
Member

@alaister alaister left a 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

@inian inian merged commit 76a7c24 into next Aug 10, 2022
@inian inian deleted the create-bucket-return branch August 10, 2022 06:31
@kiwicopple
Copy link
Member

🎉 This PR is included in version 1.8.0-next.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.0.0-rc.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants