Add doc guide for developing a new view type#344
Conversation
| The data provider's role is to provide a model corresponding to the requested method and parameters, possibly by scheduling an analysis and querying its resulting output, or any other method to extract data from the trace and compute the appropriate result. | ||
|
|
||
| ## Data Provider Factory / Descriptor | ||
|
|
There was a problem hiding this comment.
The guide below is specific for the Trace Compass server. I wonder if this should be part of the trace server specific developer guide: https://github.com/eclipse-tracecompass/org.eclipse.tracecompass/blob/master/doc/trace-server/trace-server-dev-guide.md?
I recognize that the documentation for the Trace Compass is already scattered, for example, the referenced trace server guide above has specifics for Trace Compass core AND the trace server service layer which probably should be in the repo with the trace server code. Not sure how we should handle best full-stack development that affects different layers.
I also realized that it would be hard for someone else that doesn't use the Trace Compass server to propose changes to the TSP, because the TSP yaml is generated by the Trace Compass server.
Suggestions for improving the situation are welcome.
There was a problem hiding this comment.
I think it's ok to merge it and then improve on top of this version if needed. It's good to have this documentation.
| QueryParameters queryParameters) { | ||
| ``` | ||
|
|
||
| ## TSP Typescript Client |
There was a problem hiding this comment.
Here the FE changes are outlined for a new view type. First the protocol level.
|
Any updates? |
Signed-off-by: Patrick Tasse <patrick.tasse@gmail.com>
PatrickTasse
changed the title
4 participants
What it does
Add doc guide for developing a new view type
How to test
N/A
Follow-ups
N/A
Review checklist