-
Notifications
You must be signed in to change notification settings - Fork 323
How to check the file format issues when we upload file using storage browser -AmplifyUI #6352
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
Comments
Hi @RutujaPhapale! Would you mind providing more information on what you are trying to solve with uploading files using our Storage connected component, and what your current approach is? Any sample code on what you are trying to achieve would also be appreciated. |
Hi @tiffanynwyeung , when a user uploads a non-csv file , message pop-ups-"all files failed to upload",
But i think this function is responsible for any actions which gets completed though failed, overwrite and message it is giving even when the user uploads a CSV file, I tried giving the logic to check the message format for only .csv but it is not working. My doubt is how can i check whether the file uploaded is NON-CSV and i will change message only for that. I did below changes, but then i have to change message for each and every action, for example in below i have not described any message for Pending state then no message is displayed for pending, I want to only alter the failed state, but i need to change all because for other no message is showing.
|
@RutujaPhapale, wanted to follow up here and let you know that we'll convert this issue to a feature request since this is an interesting and valid use case for Storage Browser. |
Upload a non-CSV file and verify that the appropriate error message is displayed
I have tried using the getActionCompleteMessage: (files : File[]) => {
return { content : "Please upload a CSV file" , type : "warning"}},
But above warning message appears even when i user upload a CSV file , How can i check the fille format
The text was updated successfully, but these errors were encountered: