Use relative paths in teiler#320
Merged
Merged
Conversation
djuarezgf
force-pushed
the
test/teiler-relative-path
branch
from
7ffd1f6 to
985e409
Compare
Threated
approved these changes
Jun 18, 2025
mmwaikar
pushed a commit
that referenced
this pull request
Jan 28, 2026
mmwaikar
pushed a commit
that referenced
this pull request
Jan 28, 2026
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
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.
Summary:
This update ensures that the Teiler now uses only relative references to bridgehead components. By avoiding absolute URLs, we prevent potential cross-origin issues in specific use cases.
Why:
Some environments experienced cross-origin problems due to absolute references. This change improves compatibility and flexibility across different deployment scenarios.