Consider adding a file uploader widget about vizro HOT 2 OPEN

Thanks for detailed reply @antonymilne , I agree with all you said.

It would be useful for our user research if you could explain a bit more how you might imagine this working, e.g. would you like the file to be persisted somewhere or just update things on screen in an ephemeral way?

Well, to take my use case as an example, what I wanted to build is a interface where users could upload an Excel file with known schema (i.e. column names) and it would draw a dashboard based on that. Each user upload their own version of such file in their session, and it's not shared with other users' sessions.

from vizro.

Hello @yury-fedotov, thanks very much for raising this issue - as you say, it's been asked before (actually also in #281) and I've added it to our tracker which now shows that at least 3 independent people have requested this functionality so hopefully we can bump its priority up.

Definitely I think it's a reasonable ask and it could expand usage of vizro, and I'm keen to add it as a feature. One reason it hasn't been added already, other than lots of things on the backlog with competing priorities, is that it's not quite as simple as it might sound. As alluded to in my response on #281, Dash somewhat muddies the water here because it supports at least two different ways to upload a file, and then what's also not clear on the Vizro side is what to do with the file once it has been uploaded.

It would be useful for our user research if you could explain a bit more how you might imagine this working, e.g. would you like the file to be persisted somewhere or just update things on screen in an ephemeral way? Would the uploaded file have an affect on other user's sessions or not? (As a general rule, putting something together that works for a toy project locally is much easier than coming up with a robust solution here. So if you're the only user of the dashboard and you don't care about security it's much easier to solve this upload problem. But on vizro we need to design everything robustly to work statelessly and securely so that we can scale to production with many untrusted concurrent users easily, which does make it harder to implement functionality.)

And what makes it even more complex is that Vizro solution should have a YAML API to define that widget in addition to the Python workflow.

This bit is actually not so hard since it's basically done for us by the magic of pydantic! Once we have a vizro model worked out, so long as it has field types that easily convert to JSON, this basically comes for free 🙁

from vizro.