Multiple characters trigger string

[terryli0095]

Would it be possible/are there plans to support multiple character triggers? We have a use case for r/, p/ etc. Or would it be possible to point me to the relevant code?

[andywong418]

Agreed - this would be a very useful feature!

[dabakovich]

Thanks for your feedback!
Can you provide me more examples of phrases that you can use with their triggers?

[terryli0095]

thanks for the quick response :) The r/ p/ triggers would be similar to subreddits. I think if we allow for the flexibility to enable more than single character triggers, it would make building / commands easier like /zoom, /call, or /calendar

[dabakovich]

Got it. I'll think about how to implement it soon.

One more question. There can be cases only with one or two characters (@, /, r/, /p), or there can be even more characters in the trigger?

Will it work for you to add the ability to provide a custom regex and callbacks for extracting the required parts from it (name, id)?

[terryli0095]

For me personally 2 characters is enough. Regex works for me as well! I can see how regex can be useful for other people but I can say for sure

[terryli0095]

@dabakovich btw would love to donate or support the library somehow since we are using it pretty heavily, how can we reach you?

[dabakovich]

@terryli0095 just published alpha v2.3.0-0 with POC of providing custom regex. For now, working only with regexes like trigger[name](id). But I think it enough for your testing.
Here is an example of part type configuration that supports r/ trigger:

{
  trigger: 'r/',
  allowedSpacesCount: 0,
  renderSuggestions: renderCustomTriggerSuggestions,
  textStyle: {fontWeight: 'bold', color: 'red'},
  pattern: /((r\/)\[([^[]*)]\(([^(^)]*)\))/gi,
  parsePattern: ([, original, trigger, name, id]) => ({original, trigger, name, id}),
},

Also added a "Support Me" category at the bottom of the library's home page :)

[andywong418]

Cool will test this and support ASAP!! Thank you for this :)

[andywong418]

Hi @dabakovich I seem to be getting an error trying to pay with paypal and I believe @terryli0095 has the same issue. Is there another way we could contribute?

[dabakovich]

Thanks, @andywong418! I see the problem and will try to fix it soon.
Anyway thanks for your attempt! :)

[dabakovich]

@andywong418 PayPal payment should work now.

[dabakovich]

@terryli0095 Did you test v2.3.0-0 version? Is the update works for you?

[t1amat9409]

hey @dabakovich, bumped into this issue, I think it might be a base of what I'm also trying to solve, I'm not sure if I read the comments correctly, but I'm looking to achieve a markdown similar to Hey \uFFFF@[john doe](john-doe-123), kinda got stuck trying to play around the regex

[EDIT]
I just wanna add the prefix \uFFFF to the mention value, so I looked at https://github.com/dabakovich/react-native-controlled-mentions/blob/master/src/utils/utils.ts#L354 I think this is the place to dwell on?

[rgbedin]

@dabakovich @t1amat9409 @andywong418 I have just created a pull request to insert the feature of allowing consumers of the library to specify a custom transformation for the mention value. Please check it here: #52

I am open to suggestions on it.

[dabakovich]

Hi all.

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.

You can find examples of using new v3 release here: https://github.com/dabakovich/react-native-controlled-mentions/blob/3.0/example/mentions-functional-component.tsx

To test alpha pre-release please, install the library using next command:

yarn add react-native-controlled-mentions@alpha
// or
npm install --save react-native-controlled-mentions@alpha