fix(next,ui): fixes global doc permissions and optimizes publish access data loading #6451
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.
Description
data
arg was not being populated, making this example impossible:This was because the global access route was wrongly executing the
docAccessOperation
collection operation, instead of using the explicitdocAccessOperationGlobal
for globals. This has been fixed along with tests.<PublishButton/>
on documents is one culprit for this. It performs client-side fetching for publish access and waits to render itself based on the result. This leads to the component blinking in after initial render. This has fixed by moving this logic to the server and the document info context. Now documents that are directly navigated to will immediately know its publish permission. This also meant that this property could only be accessed in that single component, as opposed to only document-wide.