Restore original behavior for URI extract functions #18612
Merged
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
This reverts commit 3befdbb which introduces a backward incompatible change to the behavior of those functions. The original behavior was intentional, and dates back to when alternatives such as try() didn't exist. Changing their behavior requires more careful consideration and exploration of possible alternatives. If we decide to break compatibility, we may need a way to restore the legacy behavior during the transition.
electrum
approved these changes
Aug 9, 2023
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.
This reverts commit 3befdbb which introduces a backward incompatible change to the behavior of those functions.
The original behavior was intentional, and dates back to when alternatives such as try() didn't exist. Changing their behavior requires more careful consideration and exploration of possible alternatives. If we decide to break compatibility, we may need a way to restore the legacy behavior during the transition.
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.