[bridge]: resolve OpenAPI spec URL dynamically based on current path #1864
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.
Problem
Swagger UI was failing to load the OpenAPI spec when served under prefixed paths (e.g. /testnet/ethereum-wrapped/openapi).
Relative paths like ../static/... were resolved incorrectly, resulting in 404 Not Found.
Solution
The OpenAPI spec URL is now derived dynamically from window.location.pathname by removing the /openapi suffix and appending the expected static spec location.
This allows the same index.html to work correctly under:
without any environment-specific configuration.