fix: Use undefined for type attribute default #5491
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.
Changes Overview
#5344 introduced a type attribute for ordered lists. The default value is set to
null
which causes a change in the outputted document when usingeditor.getJSON()
. If the user is using strict backend validation of the document, this will cause validation to fail.Changing to
undefined
removes it from the JSON document, matching previous behaviour.Pre v2.6.1
Since v2.6.1
Implementation Approach
Testing Done
Verification Steps
Additional Notes
Checklist
Related Issues
#5344