Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow CDS hooks extensions to define arbitrary JSON instead of strings #6023

Closed
AD1306 opened this issue Jun 18, 2024 · 0 comments · Fixed by #6026
Closed

Allow CDS hooks extensions to define arbitrary JSON instead of strings #6023

AD1306 opened this issue Jun 18, 2024 · 0 comments · Fixed by #6026
Assignees

Comments

@AD1306
Copy link
Collaborator

AD1306 commented Jun 18, 2024

Describe the bug
Currently, CDS hooks accepts a String for Extension and when calling cds service discovery endpoint we get a String back for extension. The same happens for request extension and response extension.

Expected behavior
CDS hooks should be able to accept arbitrary JSON and return it via discovery endpoint or in the card response if set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant