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

Send Notification during ticket assignment #2520

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

MahtabBukhari
Copy link
Contributor

Describe your changes

Issue ticket number: [#2390,#2391,#2392]

Links: (https://community.sphinx.chat/p/cs6elnatu2rsh7eq5hk0/assigned/3582/0 , https://community.sphinx.chat/p/cs6elnatu2rsh7eq5hk0/assigned/3581/1 , https://community.sphinx.chat/p/cs6elnatu2rsh7eq5hk0/assigned/3580/2)

Close: [#2390,#2391,#2392]

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have tested on Chrome and Firefox
  • I have tested on a mobile device
  • I have provided a screenshot or recording of changes in my PR if there were updates to the frontend

@MahtabBukhari
Copy link
Contributor Author

@humansinstitute Could you please review the PR?

@humansinstitute
Copy link
Contributor

@tobi-bams can you review this please when you come online?

This is an implementation of the Notification system you proposed.

}

// Contact key is available, proceed with sending
sendRespStatus := sendNotification(n.PubKey, n.Event, n.Content, "")
Copy link
Contributor

Choose a reason for hiding this comment

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

@MahtabBukhari please can we have a different function that sends only the notification because by calling the sendNotification function we are doing a lot again. We are getting the user details trying to get contact_key but we already have that, we are also saving the notification again and we don't need that, we just want to send the notification because we are sure the bot has added the user.

I will suggest we make the sending /send a different function and we can use it here and also use it in the sendNotification function.

We might also want to change the sendNotification name to something like processNotification and the actual function that calls the /send send endpoint can be called sendNotification.

Please lemme know if this makes sense.
Great Job man!!

Copy link
Contributor

@tobi-bams tobi-bams left a comment

Choose a reason for hiding this comment

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

@MahtabBukhari I see some changes not related to this PR, please can you undo that?

@MahtabBukhari MahtabBukhari force-pushed the Verify_User_and_Send_Notification branch from e64af42 to 121d831 Compare February 5, 2025 19:34
@MahtabBukhari
Copy link
Contributor Author

@tobi-bams please review it now

irrelative unit tests failed

image

@MahtabBukhari
Copy link
Contributor Author

@humansinstitute could you please review this 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.

3 participants