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
It seems to me that the settings not enough the ability to completely disable the replacement of tokens.
You did not think to change the syntax of tokens to a more exotic one? ${token} is used in too many projects and is de facto the standard for value substitution (along with %token%). This leads to a lot of conflicts.
Could it be worth changing it to, for example, @ <token>? (I have never met such an variant).
It is necessary to add a certain keyword/sequence of characters, which will say that this token should not be replaced.
That is, if the user enters /s (or another) when requesting the ${very_very_long_long_token_name} token, the plugin does not touch this token.
The text was updated successfully, but these errors were encountered:
It seems to me that the settings not enough the ability to completely disable the replacement of tokens.
You did not think to change the syntax of tokens to a more exotic one?
${token}
is used in too many projects and is de facto the standard for value substitution (along with%token%
). This leads to a lot of conflicts.Could it be worth changing it to, for example,
@ <token>
? (I have never met such an variant).It is necessary to add a certain keyword/sequence of characters, which will say that this token should not be replaced.
That is, if the user enters
/s
(or another) when requesting the${very_very_long_long_token_name}
token, the plugin does not touch this token.The text was updated successfully, but these errors were encountered: