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
I wonder whether it would be worth implementing a Query class in FlowClient, which contains a query specification along with a run method, and status and result properties. The flowclient functions that currently return a query spec could instead return a fllowclient.Query object.
My feeling is that this might be more intuitive for users, would remove the need for them to deal directly with query IDs, and may help to avoid confusion between query specifications and query results.
The text was updated successfully, but these errors were encountered:
I wonder whether it would be worth implementing a
Query
class in FlowClient, which contains a query specification along with arun
method, andstatus
andresult
properties. The flowclient functions that currently return a query spec could instead return afllowclient.Query
object.My feeling is that this might be more intuitive for users, would remove the need for them to deal directly with query IDs, and may help to avoid confusion between query specifications and query results.
The text was updated successfully, but these errors were encountered: