feat(next): adds support for edit view description components #9763
+18
−11
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.
What?
This PR adds support for distinct edit view descriptions since there was clearly the infrastructure in place for it anyway. This also fixes an issue where collection descriptions were finding their way into document edit views.
Why?
To enable end-users to add their own custom components as descriptions in edit views.
How?
By allowing a new
Description
custom component in theadmin.components.views.edit
object.Before:
Description-before--Payload.webm
After:
Description-after--Payload.webm
Notes:
I noticed that none of the custom components inThis was fixed.renderDocumentSlots
are actually getting passed default props. I decided it was likely out of scope for this PR, but can easily add this in.