You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying out this component to drop DICOM files. While they are typically associated with the .dcm extension, it is also common for the files not to specify an extension at all (e.g. the file name being just I_00001). In these cases, while the media type is still application/dicom, they will not show up on the file upload form when accepting only this type, and even when selecting them here or dropping them
to the drop zone, they will be always excluded with the error "I_00001 is not a valid file type" (code 1) if they do not have an extension.
<FilesonChange={handleChange}onError={handleError}accepts={['application/dicom']}maxFileSize={100_000_000}clickable>
Drop files here or click to upload
</Files>
I tried several combinations of accepts, including '*/*', '', '.*', '*.*', and '*', but none of them worked. Is there something that can be done to work around this? Or are changes to the library necessary to support this?
The text was updated successfully, but these errors were encountered:
I was trying out this component to drop DICOM files. While they are typically associated with the .dcm extension, it is also common for the files not to specify an extension at all (e.g. the file name being just
I_00001
). In these cases, while the media type is stillapplication/dicom
, they will not show up on the file upload form when accepting only this type, and even when selecting them here or dropping themto the drop zone, they will be always excluded with the error "I_00001 is not a valid file type" (code 1) if they do not have an extension.
I tried several combinations of
accepts
, including'*/*'
,''
,'.*'
,'*.*'
, and'*'
, but none of them worked. Is there something that can be done to work around this? Or are changes to the library necessary to support this?The text was updated successfully, but these errors were encountered: