UFM: Adds $index support to Block editors (fixes #20470)
#20488
Merged
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
Fixes #20470.
When authoring UFM labels for Block editors (Block Grid, Block List and RTE Blocks), you can now use a
$indextoken to display the block's current index (zero-based).To note, with RTE Blocks, the index will always be zero
0. It has been wired up so that if we do implement index ordering for RTE Blocks in future, then it will render correctly.How to test?
On a document that has a Block List or Block Grid, configure the corresponding data-type to have a label that utilizes the UFM syntax, e.g.
Block ${ $index + 1 }. When adding several blocks, the block label should render the$indexin a sequential order.