- Issue created by @kunalkursija
- š¬š§United Kingdom longwave UK
The preview endpoint could probably return additional data to achieve this.
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
I think it's not the
experience_builder.api.previewroute that should provide that info, butexperience_builder.experience_builderitself? š¤Because:
experience_builder.experience_builderis requested once, and the information should be retrieved thenexperience_builder.experience_builderis requested N times (once per component placement/props change), and it is completely unaware of the underlying content entity being edited
But perhaps @longwave sees a reason for using
experience_builder.api.previewthat I'm missing? š¤ - š¬š§United Kingdom longwave UK
If the user changes the page title inside XB, should it update immediately (ie. on preview)?
- š«š®Finland lauriii Finland
The page title should update automatically as it's being changed.
- š¬š§United Kingdom longwave UK
I guess another question is what should be displayed here: just the entity title/label? Or the HTML
<head>title? - š«š®Finland lauriii Finland
That's a good question. I think it should be just the entity title/label since that's what we would be using for referring to the page else where.
- š®š³India Anjali Rathod
I will be working on the API part of this issue and then my colleague parthbcharya will take over the FE work. Iām unclear about which API to use for my current task in experience_builder. Should I leverage an existing API route, extend one of the current routes, or consider creating a new API from scratch?
Iād appreciate some guidance to understand the best approach for this scenario.
- š¬š§United Kingdom longwave UK
Given the discussion in #7-11 I still think the preview endpoint is the best place to add this to the API.
I suggest adding the title to the JSON response in
XBPreviewRenderer::renderResponse(); it looks like we might be able to capture the title inprepare().
