Remove "clever" decoding from _sanitizePath
#29
Merged
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.
I had previously updated the
ImgixClient._sanitizePath()
method in an attempt to be clever and properly handle pre-encoded paths. This introduced unnecessary complexity into the method (detemining whether or not a given string is unencoded, sorta pre-encoded, or fully pre-encoded is trickier than it seems at first glance) and introduced stupid bugs into its base use-case.Having failed my attempt at cleverness, I am suitably chagrined. This PR removes all code dealing with pre-encoded paths from
ImgixClient._sanitizePath()
so it only handle non-encoded inputs. Our README has instructed users to only pass in non-encoded data from the start:This also fixes #28, and includes a new test case to ensure non-URL paths with spaces are handled properly.
@oaleynik Would you care to review these changes for me?