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
It would be very useful both for debugging and for new developers to have a high-level sequence diagram for BTE's query handling, either of the general sync endpoint or just starting from the query_graph_handler.
Optimally, this diagram would establish an explanation of the flow of data between each of the primary handler classes, grouped by file/module. Exact methods needn't be documented however the data structures/types (using the new vocab) moving between each handler should be annotated.
Making this diagram would entail stepping through the entirety of the lifecycle of a request, following all major data structures as they are created or obtained, and carefully organizing the diagram to display the module-handler hierarchy and how it interacts in the lifecycle of a request.
It would be very useful both for debugging and for new developers to have a high-level sequence diagram for BTE's query handling, either of the general sync endpoint or just starting from the
query_graph_handler
.Optimally, this diagram would establish an explanation of the flow of data between each of the primary handler classes, grouped by file/module. Exact methods needn't be documented however the data structures/types (using the new vocab) moving between each handler should be annotated.
Making this diagram would entail stepping through the entirety of the lifecycle of a request, following all major data structures as they are created or obtained, and carefully organizing the diagram to display the module-handler hierarchy and how it interacts in the lifecycle of a request.
https://mermaid-js.github.io/mermaid/#/sequenceDiagram seems like a good tool to do this using markdown so it can be version controlled
The text was updated successfully, but these errors were encountered: