Is there a workaround for this?
I'll post on this thread when we ship a fix!
I'm probably a little late to this, but we have been using a temporary workaround via modules.
Hope this helps!
I am surprised it has taken me this long to realize the potential utility to have JS queries in the Query Library.
Since it could probably not see the calling app's state, I can see some limitations that would be fine with me:
You would need to pass all state into the query and return a result to communicate with the app. If the JS query triggered any other queries, they would need to themselves be on the query library.
My use case is I am running a series of actions that are duplicated in three different apps. They were rather simple until the client wanted them to do a lot more. There is no good way to modularize the actions as Modules do not have a "reason"able and reliable way for the parent to trigger one of it's query on demand.
Thank you for sharing these details, @bradlymathews! I shared this feedback internally as well