Update flutter_quill_delta_from_html on pubspec.yaml to fix current issues #1999
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
In the current version of flutter_quill_delta_from_html (1.2.1) html is not supported within a
<div>
and there are even errors during the parsing of thefont-size
to a valid value forflutter_quill
.With this new version the inclusion of
<div>
is officially in the package forHTML
like this:Will converted on:
And an important point was fixed, which is the parsing of the
font-size
andline-height
, where if before we used values like:rem
,em
,pc
,pt
, etc. the editor threw errors because those values were not valid referenced in this comment:Previously if we had a:
The parsing to
Delta
was:Which caused errors in the rendering. Now, with the addition of parsing and calculation based on the unit type, the
Delta
will have an output such that:The default values:
0.75em
,1.5em
, and2.5em
will be equivalent to:small
,large
andhuge
Related Issues
Fix #1994
Fix #1990 (comment)
Checklist
CHANGELOG.md
nor the package version inpubspec.yaml
files../scripts/before_push.sh
and it all passed successfullyBreaking Change
Does your PR require developers to manually update their apps to accommodate your change?
!
in the title as explained in Conventional Commits).