fix: Frontend error when creating SAML configuration if API URL is relative #4751
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.
Thanks for submitting a PR! Please check the boxes below:
docs/
if required so people know about the feature!Changes
If
Project.api
points to a relative URL such as/api/v1
, clicking on "Create SAML Configuration" or opening an existing SAML configuration results in an error:This does not happen with the default
npm run dev
because we're setting an absolute URL ofhttp://localhost:8000/api/v1/
. To reproduce this bug locally, have the FE proxy requests to the BE by running like this:How did you test this code?
Manually - using
flagsmith/flagsmith-private-cloud
as the API, try to create a SAML configuration or edit an existing one.