Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[Validator] Improve Image constraint invalid mime type message#16663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
javiereguiluz commentedApr 1, 2022
Thank you Maxime. |
fancyweb commentedApr 4, 2022
It's a little bit more complicated than that.
|
mdoutreluingne commentedApr 4, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Sorry for misunderstanding this new change, indeed I will correct this as soon as possible. |
…age option (mdoutreluingne)This PR was squashed before being merged into the 6.1 branch.Discussion----------[Validator] Fix of the description of the mime type message optionIn this PR, I corrected the mistake I made [here.](#16663)I used the table of parameters of the `File` constraint to explain the different parameters in the `Image` constraint.Can you do a review please?`@fancyweb` ready for review :)Commits-------b557833 [Validator] Fix of the description of the mime type message option
Uh oh!
There was an error while loading.Please reload this page.
Fixes#16662
Changed the default message in case of incorrect mime type for the image constraint.
From 6.1 we will replace
This file is not a valid image.with thisThe mime type of the file is invalid ({{ type }}). Allowed mime types are {{ types }}..