Skip to content

Add send_notification action and update related components - #47

Closed
michaelsss1 wants to merge 1 commit into
mainfrom
Feature/notification_task
Closed

michaelsss1 wants to merge 1 commit into
mainfrom
Feature/notification_task

Conversation

@michaelsss1

Copy link
Copy Markdown
Contributor
  • Implemented SendNotificationAction for sending notifications via Feishu or WeCom.
  • Updated action registry to include send_notification.
  • Enhanced README and documentation to reflect new notification capabilities.
  • Updated frontend components to support the new notification action.

- Implemented SendNotificationAction for sending notifications via Feishu or WeCom.
- Updated action registry to include send_notification.
- Enhanced README and documentation to reflect new notification capabilities.
- Updated frontend components to support the new notification action.
if isinstance(response_payload, dict) and int(response_payload.get("code", 0) or 0) != 0:
success = False
provider_error = str(response_payload.get("msg") or response_payload.get("message") or "")
except (TypeError, ValueError):
if isinstance(response_payload, dict) and int(response_payload.get("errcode", 0) or 0) != 0:
success = False
provider_error = str(response_payload.get("errmsg") or response_payload.get("message") or "")
except (TypeError, ValueError):
return !['api_secret', 'alias_name', 'verify_tls', 'kill_states'].includes(fieldName);
type SchemaDef = { name: string; description: string; fields: FieldDef[] };

const actionSchemas: Record<string, SchemaDef> = {

@alexchen16 alexchen16 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed, reject the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants