-
Notifications
You must be signed in to change notification settings - Fork 129
Description
Context
In the List widget, we can select any dimension that may have a number of relations tied to it (the *_side fields). These are currently just opaque IDs, and appear as-is in the list display.
Use case
We want to not see the opaque IDs, but the representative of these IDs. However, we still need the opaque IDs available so that we can craft queries, URLs... with them.
Current Workaround
Not implemented: we could resolve the IDs by querying the regular OpenBAS API for the relevant entities. Not favoured as a long term solution.
Proposed Solution
Introduce a standard whereby *_side fields should be implemented as either of type
Variant A:
EsBase or Set or List to benefit from the structure's fields base_id and base_representative
Pro: standard structure in the ES related subsystem.
Con: not the primary use case for the EsBase struct.
Variant B:
EsSide with only two fields: id and representative
Pro: tailored for the use case
Con: another struct in the data model.
We would implement variant B.