Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dont use false as cache key for non utf8 path in normalizePath #22520

Merged
merged 1 commit into from
Sep 9, 2020
Merged

dont use false as cache key for non utf8 path in normalizePath #22520

merged 1 commit into from
Sep 9, 2020

Commits on Aug 31, 2020

  1. dont use false as cache key for non utf8 path in normalizePath 

    since `json_encode` returns `false` if it's input isn't utf8, all non utf8 paths passed to normalizePath will currently return the same cached result.

Fixing this makes working with non utf8 storages a *little* bit more possible for apps

Signed-off-by: Robin Appelman <robin@icewind.nl>
    @icewind1991
    icewind1991 committed Aug 31, 2020
    Configuration menu
    Copy the full SHA
    a792a51 View commit details
    Browse the repository at this point in the history