You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
I have an use case that could justify the need for an onLoaded/onComplete event for the Query component. It goes like this:
I have a select input that loads its options asynchronously based on a query. When the query loads, I need to populate my select's options and select the first option by default.
For now I can achieve this using the HOF and the (soon-to-be-deprecated) componentWillReceiveProps:
I can't see how this can be achieved using the Query component without having an event which fires up when the query has been fetched (similar to the one the Mutation component has). Any ideas?
The text was updated successfully, but these errors were encountered:
I have an use case that could justify the need for an onLoaded/onComplete event for the Query component. It goes like this:
I have a
select
input that loads its options asynchronously based on a query. When the query loads, I need to populate myselect
's options and select the first option by default.For now I can achieve this using the HOF and the (soon-to-be-deprecated)
componentWillReceiveProps
:I can't see how this can be achieved using the Query component without having an event which fires up when the query has been fetched (similar to the one the Mutation component has). Any ideas?
The text was updated successfully, but these errors were encountered: