fix: add projectId field to API key schema and update sign-up link #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@AbdulDavids is attempting to deploy a commit to the Speakeasy Team on Vercel. A member of the Team first needs to authorize it. |
Member
|
Hey Abdul. I'm sorry that I've only just seen this. Would you expand a bit on the reproduction steps for #2? I have never experienced the issue you're describing myself, and I'd like to understand the core issue before accepting the change. |
Member
|
Additionally, in your screenshot, it looks like you may be passing the API key into the field for the access token? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses two issues:
Fixes the sign-up link: The sign-up link on the sign-in page was broken and is now fixed.
src/lib/auth.tsResolves API key authentication failures: A missing field in the API key validation schema was causing
valid keys to be rejected. This has been corrected.
src/routes/(auth)/sign-in/+page.svelte