Tiberiu Ichim
Tiberiu Ichim
@sauzher Indeed, it is the job of the frontend to decide if it wants this information. With an expander, it can do that: ``` curl http://localhost:3000/somefolder?expand=default_page ``` So it would...
Just throwing https://github.com/plone/plone.restapi/pull/944 into discussion. I'm ok either way
The problem is caused by the initialValue that's being used in both editors. Use cloneDeep to wrap it, it will work properly after that.
> But, we only want to do that when necessary, because it is harder to cache. I think cache is hard to control for vocabularies, specially if they are role-based....
> We add a parameter to getVocabulary and we decide it based on where it is used, instead of adding more configuration. Sounds good, not sure how this is exposed...
> The contextuality of the vocabulary should be handled by the back-end. Then the context has to be known all the time.
> (Note that there is a separate problem to solve with the vocabularies that are serialized into the /@querystring endpoint response, which is always fetched at the site root.) @querystringsearch...
@sneridagh @tisto any insight on a visual for this?
So, let's summarize what this PR is about: With current volto, the listing block behaves like: | | SSR | clientside | |------------|-----------------------------------------|------------------------------------------------------------------| | no query | incorrectly calls getQuerystringResults...