Skip to content

Commit bb1436e

Browse files
authored
add example
1 parent 7142013 commit bb1436e

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

docs/specification/current.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -742,6 +742,34 @@ A `systemAction` is the same **[Action](#action)** which may be returned in a su
742742
}
743743
```
744744

745+
746+
> Example response using `no-guidance-but-app-launch`
747+
748+
```json
749+
{
750+
"no-guidance-but-app-launch": true,
751+
"cards": [
752+
{
753+
"uuid": "4e0a3a1e-3283-4575-ab82-028d55fe2719",
754+
"summary": "Example Link Card",
755+
"detail": "Click the link to launch github.",
756+
"source": {
757+
"label": "Static CDS Service Example",
758+
"url": "https://example.com",
759+
"icon": "https://example.com/img/icon-100px.png"
760+
},
761+
"links": [
762+
{
763+
"label": "Github",
764+
"url": "https://github.com",
765+
"type": "absolute"
766+
}
767+
]
768+
}
769+
]
770+
}
771+
```
772+
745773
## Feedback
746774

747775
Once a CDS Hooks Service responds to a hook by returning a card, the service has no further interaction with the CDS Client. The acceptance of a suggestion or rejection of a card is valuable information to enable a service to improve its behavior towards the goal of the end-user having a positive and meaningful experience with the CDS. A feedback endpoint enables suggestion tracking & analytics. A CDS Service MAY support a feedback endpoint; a CDS Client SHOULD be capable of sending feedback.

0 commit comments

Comments
 (0)