feat: use the new setup domain for lightning pages if available #650
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
amtrack
force-pushed
the
fix/use-setup-url
branch
from
c4003a0 to
63a8ef4
Compare
Opening a `/lightning/` setup page on the instance domain caused multiple server- and client-side redirects to the new setup domain. This caused errors like: > failed: Protocol error (DOM.describeNode): Cannot find context with specified id Now all lightning pages should open using the new setup domain if available and use the instance URL otherwise. Example: https://[MyDomainName].my.salesforce-setup.com
amtrack
force-pushed
the
fix/use-setup-url
branch
from
63a8ef4 to
d132451
Compare
amtrack
changed the title
|
🎉 This PR is included in version 4.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
No description provided.