Description
Currently, when all Linked VPs are removed, the service still persists, but contains an empty serviceEndpoint: []. This is unexpected from a frontend perspective since there is no data to visualize.
Note: this issue could be tackled in an upcoming refactor with clearer API design. Currently, the Linked VPs are set via their presentation_ids on a single endpoint. An improved design would contain separate commands for each user intend (AddLinkedVP, RemoveLinkedVP, ...).
Steps to Reproduce the Bug
n/a
Expected Behaviour
n/a
Actual Behaviour
n/a
Errors
n/a
Description
Currently, when all Linked VPs are removed, the service still persists, but contains an empty
serviceEndpoint: []. This is unexpected from a frontend perspective since there is no data to visualize.Note: this issue could be tackled in an upcoming refactor with clearer API design. Currently, the Linked VPs are set via their
presentation_ids on a single endpoint. An improved design would contain separate commands for each user intend (AddLinkedVP,RemoveLinkedVP, ...).Steps to Reproduce the Bug
n/a
Expected Behaviour
n/a
Actual Behaviour
n/a
Errors
n/a