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
Description
The new debug client does not support all arguments available.
Goal
The goal is to add support for the missing arguments in the debug client.
This relates to issue #5330.
Propsed solution
The idea is to make a dynamic, yet configurable, way of displaying all possible arguments by reading the schema and dynamically add the arguments to the debug client. This would mean that changes in the schema would be automatically reflected in the debug client. The configurable part will perhaps be an config file that will handle different aspects hard to make dynamic. For instance defining the fields that should be "fixed" on top of the page and how to handle more complex data type inputs as well as displaying more "human-friendly" names of the different arguments.
Alternative solution
As an alternative we can implement the missing arguments the same way as it has been done so far, manually for each argument.
Additional context
There has to be some design choices when it comes to where to put the new arguments and how to make the best out of the layout, so it can support a big number of arguments.
The text was updated successfully, but these errors were encountered:
Description
The new debug client does not support all arguments available.
Goal
The goal is to add support for the missing arguments in the debug client.
This relates to issue #5330.
Propsed solution
The idea is to make a dynamic, yet configurable, way of displaying all possible arguments by reading the schema and dynamically add the arguments to the debug client. This would mean that changes in the schema would be automatically reflected in the debug client. The configurable part will perhaps be an config file that will handle different aspects hard to make dynamic. For instance defining the fields that should be "fixed" on top of the page and how to handle more complex data type inputs as well as displaying more "human-friendly" names of the different arguments.
Alternative solution
As an alternative we can implement the missing arguments the same way as it has been done so far, manually for each argument.
Additional context
There has to be some design choices when it comes to where to put the new arguments and how to make the best out of the layout, so it can support a big number of arguments.
The text was updated successfully, but these errors were encountered: