Fix to accomodate automations without triggers #14274
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In the unlikely scenario that an automation somehow doesn't have its
triggerspecified, the builder would throw an error. This fix allows the builder to better react in this situation and group these automations under aNo Triggercategory in the automation screen. Anything that requires an explicit trigger to be specified is now blocked if it isn't configuredAddresses
Screenshots
Automations without a trigger grouped under the "No Trigger" category
Actions disabled for automations without a trigger.
Disabled context menu entries
Launchcontrol
Fix to accommodate automations if they do not have a trigger configured.