You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a use case in which we would like to protect arbitrary text values writen by our endusers from being registred into the database from reserved characters (notably "new line" \n).
However it seems that feature transform.value.to is forcefully unactivated in the library while transform.value.from can be used.
Unfortunately since user can edit previously registred value we need both transformers to be set in order to maintain consistency.
Could transform.value.to be available in the same way transform.value.from is ?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
We have a use case in which we would like to protect arbitrary text values writen by our endusers from being registred into the database from reserved characters (notably "new line"
\n
).However it seems that feature
transform.value.to
is forcefully unactivated in the library whiletransform.value.from
can be used.Unfortunately since user can edit previously registred value we need both transformers to be set in order to maintain consistency.
Could
transform.value.to
be available in the same waytransform.value.from
is ?Thanks.
The text was updated successfully, but these errors were encountered: