You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A breaking change was added on v2.5.14 due to this commit.
Before this change, the input parameter server_relative_url from save_binary and open_binary wasn't escaped and the string must be url escaped (eg. Shared%20Documents for Shared Documents folder).
After this change, the server_relative_url is parsed to Shared%2520Documents due to the urlib.quote method.
We're not expecting this breaking change on a patch version. No matter what, there are no tests covering any error on this change nor a proper warning on the release notes. I think that this is a change that will affect users since office365 uses spaces by default, unfortunately.
The text was updated successfully, but these errors were encountered:
perhaps a fix to this would be to first unquote and then quote again? In this scenario, if the string already comes escaped, will not cause further issues.
Hi all!
A breaking change was added on v2.5.14 due to this commit.
Before this change, the input parameter
server_relative_url
fromsave_binary
andopen_binary
wasn't escaped and the string must be url escaped (eg.Shared%20Documents
forShared Documents
folder).After this change, the
server_relative_url
is parsed toShared%2520Documents
due to theurlib.quote
method.We're not expecting this breaking change on a patch version. No matter what, there are no tests covering any error on this change nor a proper warning on the release notes. I think that this is a change that will affect users since office365 uses spaces by default, unfortunately.
The text was updated successfully, but these errors were encountered: