Add path_unencoded function #176
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
Adds a few utility functions ('Path.decoded_of_path', 'decoded_of_path')
as well, emulating the implementation of 'path'.
Signed-off-by: Andrii Sultanov <sultanovandriy@gmail.com>
dinosaure
approved these changes
Jul 22, 2024
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 is intended less as the suggested implementation (it simply follows the existing
encoded_of_pathone), but as a starting point for a discussion to include such function.Its addition is motivated by several things:
.pathinterface similar to that of.query, which has both the encoded (verbatim) and the unencoded (default) versionUri.path x |> Uri.pct_decodepath ?pct_encoder, since the encoder relies on the list of safe characters - makes little sense to create a whitelist of all characters for this.