Add support for inline expressions rendering with visitor data on GBO side #3660
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: c1ec32f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
spastorelli
force-pushed
the
steeve/rnd-8169-render-inline-expressions-on-gbo-side-instead-of-api
branch
from
2590ede to
be604d0
Compare
spastorelli
force-pushed
the
steeve/rnd-8169-render-inline-expressions-on-gbo-side-instead-of-api
branch
from
be604d0 to
9e8ebb3
Compare
…-gbo-side-instead-of-api
spastorelli
deleted the
steeve/rnd-8169-render-inline-expressions-on-gbo-side-instead-of-api
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to add support for inline expressions rendering with visitor data on GBO side so we can move the evaluation of inline expression from the API to GBO and allow for injecting dynamic claims values (e.g API keys) in code blocks/Open API block and page content.
The evaluation of inline expressions will also be removed (kept only for search indexation) from the API in another GBX PR.
Screen.Recording.2025-09-18.at.09.38.13.mov