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

feat: Firebase Notification Setup - FCM (LAN-801) #255

Merged
merged 20 commits into from
Jan 18, 2024
Merged

Conversation

marination
Copy link
Member

@marination marination commented Jan 5, 2024

ToDo:

  • Error handling
  • Enqueueing
  • Retries with backoff
  • Change how api file is stored (file perms aren't the best on v13)
  • Test on a setup (client FCM setup) (test on staging)

- Store firebase credentials
- Trigger function on version and deleted docuemtn  insertion
- Send FCM notification if right document
- FirebaseNotification class wrapper around FCM requests
Copy link
Member

@barredterra barredterra left a comment

Choose a reason for hiding this comment

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

Some thoughts:

  • Maybe rename Water Body Management Settings to Firebase Settings
  • Uploading and storing credentials as a file seems useful. But maybe we can store it outside the normal attachments (custom button "Upload File" -> show upload dialog -> own file handler -> store in site folder bench/sites/landa/firebase/credentials.json)
  • Project ID is contained in the credentials, does not need a separate settings field. never mind, not important

@barredterra
Copy link
Member

First tests in staging environment look good now (at least no more errors from firebase)

- Store Api file in sites folder. Delete file record created via file uploader (hard to overwrite)
- Renamed settings to Firebase Settings
@marination marination marked this pull request as ready for review January 16, 2024 18:38
barredterra
barredterra previously approved these changes Jan 18, 2024
in order to be able to update credentials
@barredterra barredterra merged commit f301b9a into version-13-hotfix Jan 18, 2024
7 checks passed
@barredterra barredterra deleted the fcm branch January 18, 2024 16:10
@barredterra
Copy link
Member

🎉 This PR is included in version 0.17.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants