Added doc for additional parameter for ibexa_render#3043
Conversation
Preview of modified filesPreview of modified Markdown: |
docs/release_notes/ibexa_dxp_v4.6.md
Outdated
| <div class="release-notes" markdown="1"> | ||
|
|
||
| [[% set version = 'v4.6.28' %]] | ||
| [[= release_note_entry_begin("Ibexa DXP " + version, '2026-02-04', ['Headless', 'Experience', 'Commerce']) =]] |
There was a problem hiding this comment.
This date will be changed, just wanted to have a quick draft ready
Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>
ibexa-workflow-automation-1
bot
requested review from
adriendupuis,
dabrt and
julitafalcondusza
and removed request for
a team
| {{ ibexa_render(content, { | ||
| 'viewType': 'line', | ||
| 'params': { | ||
| 'custom_param': 'custom_value' | ||
| } | ||
| }) }} |
There was a problem hiding this comment.
What happens for method: esi? One HTTP cache per custom_value I guess as it probably goes to the _fragment URL GET params. So this custom_value also need to be scalar. The best would be a link in the method raw of the table on esi to some ESI doc but there is no clearly dedicated page about that. Probably something to rework later, taking some ideas from the training.
There was a problem hiding this comment.
method: esi is also supported. And yes, that will end up as a value in the _hash GET parameter to the _fragment controller
Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>
|
3 participants
Target: 4.6 and 5.0
Doc for: ibexa/core#674
The "release notes skeleton" is something I'm experimenting with - to have the release note text ready and waiting, instead of writing it at the day of the release.