Stream: cds hooks
Topic: CDS Hooks dynamics
Bas van den Heuvel (Sep 15 2019 at 11:12):
In various discussions during the Connecthaton and over the last weeks a noticed a large difference in the approach to the CDS Hooks Card dynamics.
Some of the variations observed include:
(1) All hooks, except order-select are requested once. Order-select CDS services are recalled when the order changes. The new cards will replace the existing ones.
(2) CDS services are ordered in a list. The first server is called and the cards are shown. When the user closes this card, the next CDS Server will be called
(3) All CDS Services are updated when the context changes.
Card behavior
(1) All cards remain in place, additional CDS calls will add new cards to the list.
(2) Cards are only removed when this is explicitly done by the end-user
(3) Cards are removed when a suggestion is followed.
The specification does not state what the expected behavior is. What is the expected behavior?
Bas van den Heuvel (Oct 04 2019 at 14:50):
Copied this topic to a CDS-hooks issue on github: CDS Hooks Dynamic Behavior #504 (https://github.com/cds-hooks/docs/issues/504)
Last updated: Apr 12 2022 at 19:14 UTC
