Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default filename 'untitled' always fails extension validation
High Severity
The default filename
'untitled'has no file extension, sovalidateFileExtension('untitled')will always returnfalse— it splits on'.', gets'untitled'as the "extension", and that's not inALLOWED_EXTENSIONS. This means when a file has no name (the exact scenario this PR is fixing), the upload is rejected with a confusing error: "File type 'untitled' is not allowed" instead of proceeding with the default name. The previous behavior at least gave a clear "File name is missing" error. The workspace files route doesn't have this problem since it has no extension check.