-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger names #1911
Comments
Need more clarification and also need to address the RecognizerSet as well . |
@mareekuh FYI. You might have already found this in the trigger menu: I think the first trigger type in the Message events drop-down menu should be Message received. What is shown now is Message events What it is supposed to be: Message events Thanks. |
Yes : Message received vs Message Events |
Hey @mareekuh Here are my rough thoughts: What initiates the trigger? The major reason to include events in the first-level menu is that it might help users to understand that triggers are created to react to some type of events. Thanks. |
No I'd like to leave out the word event. https://www.figma.com/file/HLtKaKHctLldivPnzQ7BqQOI/Composer-MI-lotsotings?node-id=2663%3A15274 |
@mareekuh It looks good! Just one thing, can we add the word "trigger" to each of them? I feel it's more consistent. But this will bring another issue, some trigger names may be too long. |
We can use 'trigger' in the first menu, but don't need it again in the 2nd. |
Yes, I agree. No need to duplicate in the 2nd level menu. |
addressed via #2151 |
Is your feature request related to a problem? Please describe.
Current naming of triggers is a bit confusing.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: