At this point, I always have to import a query from the Query Library before I can use it for, let's say, a select component with numerous options.
However, I think it could be more time efficient to be able to select any queries directly from the Query Library when attaching a mapped data source.
As a result, one would no longer have to go import the query from Query Library first - and then attach it as a mapped data source.
I think there is little argument against this idea, given how queries from the query library are by their very nature static and cannot be replaced. Having duplicates inside of the code tab only adds noise and clutter, in my opinion.
Great idea. It would definitely cut down on steps and friction to getting mapped data into a component.
My first thought would be the lack of params or data type/formatting, but this can always be set the current way if needed. But error handling for incompatible datatypes might need some additional planning.
I will make this feature request and keep you updated on any news I hear about it
You mentioned "the lack of params", but as far as I know, one can only use queries from the query library without any additional params or values, right?
Good question, I was under the impression that QL queries worked with wildcards, given the Variables on the right hand side to use with double curlies as so.
I am also getting some flashbacks of trying to debug this for another user, as the Variables input field is confusing since it always shows an IDE error, and in the app the same logic {{current_user.user_id}} needs to be called again because in the second picture, in the query setup, is where this variable is actually set and is able to take in app data to pass to the query
