markup="@__id__" does not work

[Bilb]

Steps to reproduce:

1. Use a mention with the markup set as markup="@__id__" and the trigger as @
2. try to trigger a mention with @
3. nothing shows up
4. change the markup to markup="@(id)"
5. restart the app and retry the trigger. The mentions are shown

Expected behaviour: The markup does not allow the use of just __id__ Observed behaviour: The markup allows the use of just __id__

Workaround: Force edit the text on submit, looking for invalid markup matching, and replace it with was is needed. So replace all @(xxxxxxx) with @xxxxxx

[vivekcontentstack]

Facing the same problem

[ifahadashraf]

@Bilb This makes sense. Encapsulation helps the parser to identify your sensitive data.

[MortezaNajafian]

Steps to reproduce:

1. Use a mention with the markup set as markup="@__id__" and the trigger as @
2. try to trigger a mention with @
3. nothing shows up
4. change the markup to markup="@(id)"
5. restart the app and retry the trigger. The mentions are shown

Expected behaviour: The markup does not allow the use of just __id__ Observed behaviour: The markup allows the use of just __id__

Workaround: Force edit the text on submit, looking for invalid markup matching, and replace it with was is needed. So replace all @(xxxxxxx) with @xxxxxx

I have same problem but I added one space after markup like this : '__id__ ' and resolve my problem.

[drl-narola]

That's work for me.