feat: add window.location.origin backend url support #124
Conversation
This file contains 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
malmen237
approved these changes
Apr 30, 2024
martinstark
force-pushed
the
feat/osc-ready
branch
from
e76d5f8 to
d74f715
Compare
martinstark
force-pushed
the
feat/osc-ready
branch
from
d74f715 to
f26d160
Compare
martinstark
changed the title
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.
/api/v1/is not part of the API URL yet, but usingwindow.locationwon't work until the app resides in OSC anyway. It should be fine to merge this ahead of Manager/OSC support.Closes #114