Use SEAM_ENDPOINT if defined in docs #45
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
razor-x
force-pushed
the
default-endpoint-on-vercel
branch
from
2ff8c6a to
88e4162
Compare
Merged
razor-x
force-pushed
the
default-endpoint-on-vercel
branch
from
88e4162 to
54e2ee8
Compare
razor-x
changed the title
seveibar
approved these changes
Apr 27, 2023
Member
Author
|
CORS setup on the API is updated and this is now working! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Will use the real Seam endpoint (no proxy) on deployment. I suspect we will still want the local dev proxy, but can test that after this is confirmed working.