@benja-M-1 Currently detects .tar.gz, .tar.zst and .tar.bz2 being dropped and opens the normal ImportDialog, however it doesn't currently load the dropped file into the local file field. how should i go about implementing that? from what i gather, i have to extend the AppContext to include a setFile action.

Hi @eigengravy it looks promising!

i have to extend the AppContext to include a setFile action.

What do you mean by AppContext?

how should i go about implementing that?

I don't know I thought some libraries would do it. I think @felipecruz91 gave it a try and didn't managed to get the file path.

Yeah, I was not able to get the file path. I plan to look into it more.

@eigengravy I think @lucbpz might have better knowledge than me on this question :)

There doesn't seem to be an API to access the file path.

Arf, well, in this case, I don't think we should do anything when dropping a file in the extension. I fear it will be misleading. Users will think there is a bug because it doesn't fill the file path. They might even try again thinking something was wrong and have to select it with the file picker in the end, which will add more frustration and make things even worse

@felipecruz91 WDYT?

In any case, thanks @eigengravy for spending some time on that. We really appreciate that :)

Should I add a notification that dragging and dropping files is not supported?

Given that as of today it doesn't seem possible to get the absolute host path of the file imported when dragging it from the host to the extension view, I'm closing this PR.

Thank you @eigengravy for your time and effort in investigating this.