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
"As a Hive user, when I author a query in Laboratory, I would like to be able to share my query as a link (including variables and headers) with another Hive user."
The reason for this is that we then allow people to describe their problem in our supergraph support channel and include a link to the problematic query in question (likely as http deep link to the Hive Laboratory). The support can then get exactly the same state as the reporter and see what she sees when we debug and support our consumers.
This is an extremely powerful feature that will enable efficient issue resolution for the federated support channel that I think the community would love to see as part of the core Hive product. I think it would also useful for smaller/simpler graph setups as well.
The text was updated successfully, but these errors were encountered:
I just realized that since you only return mock data you might not understand why this feature is important. But this is assuming you can actually get real data out of the Laboratory; #788
I think we'll need to decide on how to implement such a feature first; either by providing an HTTP query string as a shareable link, or create a concept of Query collections that are shared across the Hive organization.
"As a Hive user, when I author a query in Laboratory, I would like to be able to share my query as a link (including variables and headers) with another Hive user."
The reason for this is that we then allow people to describe their problem in our supergraph support channel and include a link to the problematic query in question (likely as http deep link to the Hive Laboratory). The support can then get exactly the same state as the reporter and see what she sees when we debug and support our consumers.
This is an extremely powerful feature that will enable efficient issue resolution for the federated support channel that I think the community would love to see as part of the core Hive product. I think it would also useful for smaller/simpler graph setups as well.
The text was updated successfully, but these errors were encountered: