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

Regenerating project client #433

Merged
merged 2 commits into from
Nov 22, 2024
Merged

Regenerating project client #433

merged 2 commits into from
Nov 22, 2024

Conversation

stigi
Copy link
Member

@stigi stigi commented Nov 22, 2024

This incorporates the schema changes to correctly flag nullable properties (https://github.com/magicbell/magicbell/pull/5419).

The API responses did not change, and this just fixes schema validation that was previously throwing errors e.g. when a tokens discarded_at was null.

@stigi stigi requested a review from smeijer November 22, 2024 09:29
Copy link

vercel bot commented Nov 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 22, 2024 9:29am

Comment on lines +1 to +5
---
'@magicbell/project-client': patch
---

Correctly flagging nullable properties. All of them were optional before so they are likely handled correctly already and this is just affecting response validation.
Copy link
Member Author

Choose a reason for hiding this comment

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

@smeijer do you agree that this is a patch?

Copy link
Member

Choose a reason for hiding this comment

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

I do.

Copy link

pkg-pr-new bot commented Nov 22, 2024

@magicbell/cli

yarn add https://pkg.pr.new/@magicbell/cli@433.tgz

@magicbell/embeddable

yarn add https://pkg.pr.new/@magicbell/embeddable@433.tgz

@magicbell/core

yarn add https://pkg.pr.new/@magicbell/core@433.tgz

@magicbell/in-app

yarn add https://pkg.pr.new/@magicbell/in-app@433.tgz

magicbell

yarn add https://pkg.pr.new/magicbell@433.tgz

@magicbell/project-client

yarn add https://pkg.pr.new/@magicbell/project-client@433.tgz

@magicbell/magicbell-react

yarn add https://pkg.pr.new/@magicbell/magicbell-react@433.tgz

@magicbell/react-headless

yarn add https://pkg.pr.new/@magicbell/react-headless@433.tgz

@magicbell/user-client

yarn add https://pkg.pr.new/@magicbell/user-client@433.tgz

@magicbell/webpush

yarn add https://pkg.pr.new/@magicbell/webpush@433.tgz

commit: d9387cd

@stigi
Copy link
Member Author

stigi commented Nov 22, 2024

I've tested the preview build (yarn add https://pkg.pr.new/@magicbell/project-client@433.tgz) in https://github.com/magicbell/magicbell/pull/5404 and was able to confirm that it solves the issue of response validation errors on discarded_at: null for access tokens 🥳

@stigi stigi merged commit d0f7bae into main Nov 22, 2024
8 checks passed
@stigi stigi deleted the regenerating-project-client branch November 22, 2024 09:48
@MagicBella MagicBella mentioned this pull request Nov 22, 2024
stigi pushed a commit that referenced this pull request Nov 22, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @magicbell/project-client@0.5.4

### Patch Changes

- [#433](#433)
[`d0f7bae`](d0f7bae)
Thanks [@stigi](https://github.com/stigi)! - Correctly flagging nullable
properties. All of them were optional before so they are likely handled
correctly already and this is just affecting response validation.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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