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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing support to constrain allowed content types #157
Labels
Comments
thet
added a commit
that referenced
this issue
Mar 13, 2024
…ontentTypes" attribute on file and image fields. Fixes: #157
thet
added a commit
that referenced
this issue
Mar 13, 2024
Support to constrain files to specific content types with a "allowedContentTypes" attribute on file and image fields. Fixes: #157
This was referenced Mar 13, 2024
thet
added a commit
that referenced
this issue
Mar 14, 2024
Support to constrain files to specific content types with a "allowedContentTypes" attribute on file and image fields. Fixes: #157
thet
added a commit
that referenced
this issue
Mar 14, 2024
Support to constrain files to specific media types with a "accepted" attribute on file and image fields. Fixes: #157
thet
added a commit
that referenced
this issue
Mar 14, 2024
Support to constrain files to specific media types with a "accept" attribute on file and image fields, just like the "accept" attribute of the HTML file input. Fixes: #157
thet
added a commit
that referenced
this issue
Mar 15, 2024
Support to constrain files to specific media types with a "accept" attribute on file and image fields, just like the "accept" attribute of the HTML file input. Fixes: #157
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently only the image field supports a validation mechanism to check if the uploaded file has the content type "image/*".
The file type should support a similar mime/content type checking mechanism too.
The text was updated successfully, but these errors were encountered: