[
https://issues.apache.org/jira/browse/LABS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706513#action_12706513
]
Simone Gianni commented on LABS-361:
------------------------------------
Due to how converters are implemented, when a meta-type (like richtext) is
used, often double conversion occurrs. The first conversion is from the
underlying type (like string) to the meta type, the second is from the metatype
back to string to display it. When the content is modified by a form, it again
happens twice.
If conversion is rather simple, this poses no problem, but the whole idea
behind underlying meta types is to offer better conversion and validations, so
most probably converters will not be that simple.
This can be desiderable in some context, for example if I'm migrating an
already existing database that contains rich text fields, but previous contents
were unfiltered, filtering them upon load can ensure proper formatting of the
page, or while changing validation settings dureing developement.
But it is overkill for most situations, and wastes a lot of cpu time parsing
and reparsing HTML.
> [richtext] Make parsing of loaded strings optional and not always present
> -------------------------------------------------------------------------
>
> Key: LABS-361
> URL: https://issues.apache.org/jira/browse/LABS-361
> Project: Labs
> Issue Type: Improvement
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Fix For: Current
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org
For additional commands, e-mail: labs-h...@labs.apache.org
