gatsby
gatsby copied to clipboard
fix(gatsby-core-utils): decode uri-encode filename for remote file
Description
Tried decode url-encoded filename before to store remote file. So it can be served properly via generated publicURL
Related Issues
Fixes #35636
This looks like something we would like to add test case for (to prevent regression in the future)
@pieh do you think is a unit test ok? or should it be e2e?
@pieh do you think is a unit test ok? or should it be e2e?
e2e would be most welcome (that gives highest level of confidence), but I think unit test will be enough given that https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-core-utils/src/tests/fetch-remote-file.js tests entire fetchRemoteFile pipeline (not just naming helper function)
@pieh added a test, but it seems some unrelated unit test is failing in the CI
Fixed to handle file directory correctly in other cases @Boronare mentioned
(No idea about test setup failure, I'll keep rebasing)
@pieh @LekoArts could you help me to merge this change?
ok it now pass all tests except Cloud Tests
Can it be merge soon?