Conversation
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| await waitlist.join({ emailAddress }) | ||
| } | ||
|
|
||
| if (waitlist.id) { |
There was a problem hiding this comment.
Does waitlist contain a status?
There was a problem hiding this comment.
It does not, it's a single-step submission
Co-authored-by: bryce <bryce@clerk.dev>
9adef8b to
9300ff8
Compare
The Waitlist resource doesn't use the "Future" API pattern, so rename the docs accordingly and update all references. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
| sdk: js-frontend | ||
| --- | ||
|
|
||
| The `Waitlist` object provides methods and properties to manage waitlist entries in your application. It is used when you want to build a custom waitlist UI instead of using the prebuilt [`<Waitlist />`](/docs/reference/components/authentication/waitlist) component. |
There was a problem hiding this comment.
| The `Waitlist` object provides methods and properties to manage waitlist entries in your application. It is used when you want to build a custom waitlist UI instead of using the prebuilt [`<Waitlist />`](/docs/reference/components/authentication/waitlist) component. | |
| The `Waitlist` object provides methods and properties to manage waitlist entries in your application. It's useful for building a [custom flow](!custom-flow) instead of using the prebuilt [`<Waitlist />`](/docs/reference/components/authentication/waitlist) component. |
There was a problem hiding this comment.
@brkalow We prob want to add SDK-specific examples on top of the Next.js, like the other hooks have. So you'd need to use the <If /> component to have examples for Expo, React, React Router, Tanstack React Start and Chrome Extension on top of Next.js. We can remove Remix tho from the frontmatter, as we've done so for all other hooks.
|
for testing expo, is it |
|
Its just |
|
just need to test expo, having issues as one usually does with expo. |
|
@alexisintech It'll be from |
Co-authored-by: Michael Novotny <manovotny@gmail.com>
hmm yeah i figured and i had tried it but its not coming up as exported
|
|
update: chris and i are on it to figure out expo stuff 😎 |
|
@alexisintech we were missing some exports clerk/javascript#7609 will be merging soon once we get the tests passing again. |
|
went to start my expo app and its giving this error despite not having anything google set up in the app at all. it's using the plain email/password auth flows. cc @chriscanin
|
|
@alexisintech Looking into this when I get a chance! |
|
Any updates @chriscanin? |
|
@manovotny Yes, @alexisintech has tested the canary release for the fix here: #2916 (comment) @alexisintech has reported a type issue with the publishable key. I am looking into that now, but this PR should resolve the issue that we see above as well. Looks like this was happening in multiple PR's. |
what i've been doing is merging pr's into core-3 if the only thing they're waiting on is the expo sdk, and then before core-3 ships, i'm going to do a full sweep and test all the expo examples - as to not block anymore pr's that are only waiting on the expo sdk so we can go ahead and merge this one in |




This pull request contains changes generated by a Cursor Cloud Agent