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
Currently viewing the Scan Report fields / values along with their Scan Report Concepts happens on the "frontend" Next client.
For example to display the values page UI, it runs as:
Fetches the Scan Report Values by API
Fetches the Scan Report Concepts based on the values ID's by API
Combined them into an object.
Renders in a table.
This is annoying for a few reasons:
Multiple database queries, and serialisation to API
Prevents any filtering / sorting model on the Scan Report Concepts.
Combining on the client can be slow.
Instead I propose moving this functionality completely to the backend API. A new endpoint named ?? will list the combined Scan Report Values + Concepts in nested objects.
By moving to the backend, it will:
Enable filtering/sorting on the Concept level.
Possibly make this page faster, but this depends on how the database queries are able to be produced.
Fetching all Values/Concepts in one query might be cleaner and easier to enable filter/sort.
But it is possible that duplicate Concepts are being fetched / serialised, and we are losing this optimisation.
The text was updated successfully, but these errors were encountered:
Currently viewing the Scan Report fields / values along with their Scan Report Concepts happens on the "frontend" Next client.
For example to display the values page UI, it runs as:
This is annoying for a few reasons:
Instead I propose moving this functionality completely to the backend API. A new endpoint named
??
will list the combined Scan Report Values + Concepts in nested objects.By moving to the backend, it will:
The text was updated successfully, but these errors were encountered: