[Bug] Wrong error message on one filetype for FileUpload

[krikru95]

Is there an existing issue for this?

• I have searched the existing issues

Have you updated FilePond and its plugins?

• I have updated FilePond and its plugins

Describe the bug

We are using Filepond through laravel filament and if we configure a FileUpload Field with only one allowed mimetype and upload a not allowed file type we get a wrong error message.

Configuration: ->acceptedFileTypes(['video/mp4]);

Error Message: "Erwartet oder video/mp4", the correct message would be "Erwartet video/mp4", without the "oder" (or).

I created an issue for filament and they linked to this plugin.

Reproduction

1. Configure a FileUpload Field in a form with filament
   

2. Allow only on FileType
   

3. Upload one not allowed file
   

Environment

- Device:
- OS:
- Browser: all

[rikschennink]

Thanks for reporting, will look into it.

[mathieutu]

Hey.
I was opening the issue on filepond repo.
Even with a basic filepond instance, we have this issue in the case of only on type passed.

https://codesandbox.io/p/sandbox/filepond-plain-javascript-24i1m
https://codesandbox.io/p/sandbox/peaceful-waterfall-8wgxnn

[rikschennink]

@mathieutu not sure what I should be seeing on the code sandbox, it just loads files?

[mathieutu]

Oups sorry wrong link. Here it is @rikschennink:
https://codesandbox.io/p/sandbox/peaceful-waterfall-8wgxnn

[rikschennink]

Thanks!

I don't know why you wouldn't set fileValidateTypeLabelExpectedTypes to "Expects files of type 'foo'"?

[mathieutu]

Not sure to understand.
The point here is the provided translations are not working with only one mime type.
It sure can be overwritten, but what would be the point to invest time to provide default literals and translations if they do not work properly?

Also, it's not always easily configurable depending on the project/framework. For instance, in the example quoted by @krikru95, Laravel Filament load the proper configuration depending on the app current language. You can override it, but then you lose an easy out-of-the-box i18n.
(They even try to handle this issue for the English language)

One easy fix would be to have something less fancy and use something like Expects file(s) of type(s) "{allTypes}". (allTypes is allready passed, as a list of all types spearated by comma).