Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
99a7778 to
b378104
Compare
cpvalente
left a comment
There was a problem hiding this comment.
If I understand this correctly, the browser APIs are not supporting non-utf characters as first class citizens.
In that case, we shouldnt try to fight against it since we may just be pushing hard to trace problems down the road.
I would suggest we make no change
|
not quite The annoying thing is that we do allow a project title to include those letters, and if we download that project it has those correct letters, but then when it is uploaded again it gets mangled |
Makes sense, but the point still stands. Would we not be fighting the tooling and potentially pushing the problem further into the code? it sounds like the best thing would to not allow projects with those characters. I am specifically thinking of non Carolinian alphabets like Chinese which could become problematic in a way we just can’t handle it |
|
fixed up-stream, waiting for release |
allows characters like
æ ø åto be used in filenamesalso axios hadles the Content-Type automatically for multipart/form-data encoding
Watch for changes here expressjs/multer#1210