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
You know me of course, i was writing a test for the tag. As its an alias of {lowercase}{/lowercase} should an other instance of in a reponse not be an alias of {lowercase}{/lowercase}?
Speak with you soon,
Johnny
The text was updated successfully, but these errors were encountered:
PS: This is currently not the case on play.rivescript.com. That's why I am asking I was implementing that and double-checking my test on play.. But it only references so the first *. And how then about the other aliases like and (maybe i forget 1 or 2).
The shortcut tags like <uppercase>, <lowercase>, <formal> and <sentence> only translate to affecting the <star1> tag, for the very niche use cases of simple triggers like:
+ my name is *
- <set name=<formal>>Nice to meet you, <get name>.
I could consider an extension to the language to add numbers to these tags to specify which stars, like <uppercase1> thru <uppercase9> (stars 1-9 are officially documented but some/most implementations may support arbitrary numbers of stars beyond just 9, I'm not sure off hand which do), but as currently defined it's only a shortcut for <star1>
Hi!,
You know me of course, i was writing a test for the tag. As its an alias of {lowercase}{/lowercase} should an other instance of in a reponse not be an alias of {lowercase}{/lowercase}?
Speak with you soon,
Johnny
The text was updated successfully, but these errors were encountered: