-
Notifications
You must be signed in to change notification settings - Fork 76
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
FEATURE: add topic tags changed trigger to chat integration #208
Conversation
add description on how to use the placeholder
Add tests to new method
If triggered when a topic tag is changed, message behavior will follow what user defined in message.
Added migration to handle the migration of the `tag_added` filter from the chat-integration plugin. Only removed the logic from the plugin, data removal will happen in a future PR
}) | ||
channel.rules | ||
.filter((rule) => { | ||
return rule.filter !== "tag_added"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it'd be better to only allow from a list rather than blocking this one type specifically?
# frozen_string_literal: true | ||
class MigrateTagAddedFromFilterToAutomation < ActiveRecord::Migration[7.1] | ||
def up | ||
if defined?(DiscourseAutomation) && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this entire logic should be wrapped in a begin/rescue
b/c we don't really want this migration to FAIL if in the future, some of these classes change or something... It's risky to write migrations with logic referencing specific classes like this. Yeah I think rescueing errors would be good.
…t with available filters
No description provided.