-
-
Notifications
You must be signed in to change notification settings - Fork 533
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
FilePicker component #3745
FilePicker component #3745
Conversation
If you upload multiple files and then remove one of them, other files start to re-upload again(progress shows). You can test with larger files. |
I know. I copied that example from a user example, he's uploading the first file on file change. So that behaviour seems normal, right? Makes sense to trigger files changed again once a file is removed. Most cases my guess is that File Picker upload is going to be through the upload button which is not implemented yet. Edit : to add on to that, there is a new file status to keep track whether file has been uploaded already or not. |
Yes an API that can have a file streamed to. If the streaming capability is already abstracted... the better, I just can't seem to make it work locally, at least I haven't yet. Ideally we would just need to pass in the stream in... like in the blazor docs examples
|
PS: Ideally your API should already work with the native InputFile for Blazor with > 2GB in WASM. |
Ok what I have is this using IRemoteStreamContent there was some issue using vanilla stuff with abp.io But If you got code and just want an API just send me it and I´ll publish onto our dev environment for you to use and send you the URL, no problem! |
Hello, If you can just send over email (it's on my profile) the endpoint I need to invoke and how to, I'd appreciate it. |
Either that, or if you could take the time to test it yourself, but I understand that you might be quite busy also... :) |
So trying it out with @sturlath 's api.... I haven't even started trying to use Blazorise's FilePicker to try to stream the huge files, just straight up clearing it first with Blazor's Here's the code... (Same file uploads fine through @sturlath 's swagger....) |
Well I just found this post, dotnet/aspnetcore#43388 // dotnet/runtime#36634 this explains why I wasn't being successful streaming with a local api eitherway. So it is seeming to me that even tough they fixed the 2gb constraint you'll still have some kind of limitations related to memory management when handling bigger files on WASM I guess? @sturlath have you actually managed to work around wasm and "big files" in any of your implementations with other |
…Async. Update notification events to make sure they use the renderer's thread.
@stsrki go ahead and re-take a look at this when you have time. |
Closes #3250
Closes #1184