Clarify behavior of parse_url_opts with regards to case sensitivity
#613
Conversation
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
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
AdamGS
changed the title
AdamGS
changed the title
parse_url_opts with regards to case sensitivity
kylebarron
approved these changes
Jan 22, 2026
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.
Which issue does this PR close?
Related to #529
Rationale for this change
Clarify the behavior of
parse_url_opts, while the variousfrom_env()functions do mention they only support case sensitivity, it does seem like multiple users have tried to useparse_url_optsand ended up with pretty confusing problems.What changes are included in this PR?
Small enhancement to docs
Are there any user-facing changes?
No