AI oneshots should not be blocking actions #61
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
when I fire off a one-shot, the activity blocks first, then when results are there, it shows results. The blocking must happen in the UI elements where it is shown (for example with the "KI analysieren" or the taxonomy suggestions). In general, there should be no blocking activities that lock up the UI, everything that can run longer must be linked to an UI element that shows that there is a thread in the background we are waiting for. So one-shot AI activities should be run on a separate thread and the UI should show that we are waiting for results from that thread and then update automatically when the results come back. This should happen for all situations where there are oneshot activities, so post editor quick actions, automatic actions like automatic translations, quick actions on media, etc.
implemented via github