Skip to content

fix: preserve UTF-8 GraphQL upload filenames with latest graphql-upload#1

Closed
coratgerl wants to merge 1 commit into
alphafrom
fix-file-encodage
Closed

fix: preserve UTF-8 GraphQL upload filenames with latest graphql-upload#1
coratgerl wants to merge 1 commit into
alphafrom
fix-file-encodage

Conversation

@coratgerl

Copy link
Copy Markdown
Owner

Summary

  • upgrade graphql-upload to the latest ESM-only release while keeping Parse Server on its current public module model via a small private compatibility helper
  • preserve accented GraphQL upload filenames end-to-end by forcing UTF-8 multipart filename decoding, encoding the internal /files handoff safely, and allowing accented characters through filename validation
  • add a GraphQL regression test covering café.txt uploads and keep existing GraphQL upload coverage green

Test plan

  • Run the focused GraphQL regression for accented filenames
  • Run spec/ParseGraphQLServer.spec.js
  • Run targeted spec/ParseFile.spec.js filename checks
  • Run npm test

Made with Cursor

Load the latest ESM-only graphql-upload through a small compatibility layer so GraphQL uploads keep accented filenames intact without changing Parse Server's public module model.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coratgerl coratgerl closed this May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant