Added optional getMentionValue for allowing custom mention values #52
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.
In order to be able to achieve custom mention values that does not follow
${trigger}[name](id)
, an optionalgetMentionValue
was added to theMentionPartType
type.By modifying the
getMentionValue()
function fromutils.ts
we are now able to allow the consumer of the library to specify whatever pattern they want for the mention transformation.The consumer also has to specify
pattern
andparsePattern
so the library can also parse the text in the input properly as the user types. Maybe there is a better way of combining all of those. I am open to suggestions.Example of code that allows the user to specify a different pattern (i.e.
\uFFFF@[Jack](123)
):You can easily combine this with
react-native-parsed-text
and usemyMentionRegex
to also convert the text into a human-readable format as you wish.