Conversation
java/fiori-drafts.md
Outdated
| When setting `cds.drafts.persistence` to `split` only queries that are specified by the SAP Fiori draft orchestration are supported. | ||
| ::: | ||
|
|
||
| ::: Aggregation Queries |
There was a problem hiding this comment.
| ::: Aggregation Queries | |
| ::: info Aggregation Queries |
You have to specify a container type. Possible values: info, tip, warning, danger, details, code-group, raw.
java/fiori-drafts.md
Outdated
| When setting `cds.drafts.persistence` to `split` only queries that are specified by the SAP Fiori draft orchestration are supported. | ||
| ::: | ||
|
|
||
| ::: warning Aggregation Queries |
There was a problem hiding this comment.
I have two thoughts:
- two warnings next to each other? Can we avoid that?
- It feels like this warning could be a subsection with its own L3 header. WDYT?
There was a problem hiding this comment.
Here's a collaborative code review enhanced by AI assistance. These suggestions offer potential improvements and insights to consider, though they're recommendations rather than requirements. You have full creative control over your code—AI simply provides additional perspective to support your decision-making process. Use whatever feels valuable and aligns with your project goals.
Model: claude-sonnet-4-20250514 | Prompt Tokens: 941 | Completion Tokens: 163
Co-authored-by: René Jeglinsky <rene.jeglinsky@sap.com>
|
@MattSchur @renejeglinsky I haven't merged it so that you can have a chance to review my edit. |
No description provided.