Skip to content
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

Add support for WhatsApp templates not syncing notfications #398

Merged
merged 1 commit into from
Mar 4, 2024

Conversation

norkans7
Copy link
Contributor

@norkans7 norkans7 commented Mar 1, 2024

Copy link

codecov bot commented Mar 1, 2024

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 78.68%. Comparing base (4bd9569) to head (2db805f).

Files Patch % Lines
src/list/NotificationList.ts 0.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #398      +/-   ##
==========================================
- Coverage   78.69%   78.68%   -0.02%     
==========================================
  Files          78       78              
  Lines       20994    20997       +3     
  Branches      686      686              
==========================================
  Hits        16521    16521              
- Misses       4466     4469       +3     
  Partials        7        7              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -76,6 +76,9 @@ export class NotificationList extends TembaList {
} else if (notification.incident.type === 'channel:disconnected') {
icon = Icon.channel;
body = 'Your android channel is not connected';
} else if (notification.incident.type === 'templates:unsynced') {
Copy link
Member

Choose a reason for hiding this comment

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

I think i'd call this something like channel:templates_failed since like channel:disconnected it applies to a specific channel... and we're not syncing so much as fetching.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That is more than 20 characters limit we have on Incident type.
Should I change the limit there to like 32 or 64? @rowanseymour

Copy link
Member

Choose a reason for hiding this comment

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

Just wanted to reiterate how unfortunate it is this requires a component change.

Copy link
Member

Choose a reason for hiding this comment

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

@norkans7 yeah let's do 32

@ericnewcomer maybe not ideal but we're adding new incident types very rarely.. like contact event types for the chat component

Copy link
Member

Choose a reason for hiding this comment

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

I guess I'm still on the fence about JSON endpoints returning HTML...

@norkans7 norkans7 force-pushed the WA-templates-sync-incident branch from 1ab2e47 to 2db805f Compare March 1, 2024 15:29
@rowanseymour rowanseymour merged commit 758643b into main Mar 4, 2024
2 of 4 checks passed
@rowanseymour rowanseymour deleted the WA-templates-sync-incident branch March 4, 2024 16:35
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants