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
In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before executing the queries, user would know the complexity/depth value of them.
Another important concern is that eventhough we have named this tab as "Complexity Analysis", there is no analysis doable via that tab. It only displays the complexity values ATM. So the current implementation of the tab is not doing what it says as doing.
If we add a capability as $subject this tab name "Complexity Analysis" would be meaningful.
Describe your solution
Should be possible to re-use/adapt the implementation of GraphQLQueryAnalysisHandler to implement this improvement.
The text was updated successfully, but these errors were encountered:
Describe your problem(s)
In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before executing the queries, user would know the complexity/depth value of them.
Another important concern is that eventhough we have named this tab as "Complexity Analysis", there is no analysis doable via that tab. It only displays the complexity values ATM. So the current implementation of the tab is not doing what it says as doing.
If we add a capability as $subject this tab name "Complexity Analysis" would be meaningful.
Describe your solution
Should be possible to re-use/adapt the implementation of GraphQLQueryAnalysisHandler to implement this improvement.
The text was updated successfully, but these errors were encountered: