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
The MentionInput currently formats the selected tag items as @Selected_Tag. And in the actual text value it will be provides as @ [ Selected_Tag](TagID) from the data model. But the issue I face here is it will follow the same thing when user enter a text as follows: @ [ What is going on]( hello ) This will get formatted as @what is going on and will be shown to the user as a tag. @dabakovich Is there anyway that we can escape this user entered string which matches the regex (style it like the normal text, so it does not look like a tag) and consider only the actual tags to look as tags.
The text was updated successfully, but these errors were encountered:
Thanks for your feedbacks. For now, unfortunately, we can't avoid this. The core concept of the library is to store the whole value as plain text, not as an array of parts. However, in the future (likely in the next v3 release), you will be able to provide your custom mention pattern that could be more complex.
I'm glad to say that v3 release is coming with few core improvements. One of the new features is full support of multiple characters trigger and custom regex pattern for mentions.
The MentionInput currently formats the selected tag items as @Selected_Tag. And in the actual text value it will be provides as @ [ Selected_Tag](TagID) from the data model. But the issue I face here is it will follow the same thing when user enter a text as follows: @ [ What is going on]( hello ) This will get formatted as @what is going on and will be shown to the user as a tag.
@dabakovich Is there anyway that we can escape this user entered string which matches the regex (style it like the normal text, so it does not look like a tag) and consider only the actual tags to look as tags.
The text was updated successfully, but these errors were encountered: