Feat/mobile/notifications #214
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The User struct in database.go has been updated to include a new field called ExpoPushToken. This field will store the Expo push token for a user, allowing for push notifications to be sent to specific users. This change was made to support the new functionality of retrieving push tokens for specific users.
…-SE-2024/occupi into feat/mobile/notifications
…for actual functionality
…otifications. Now we need to integrate with frontend. Additional new endpoints are get-notifications for users as well as get-users. They also allow for filtering functionality. Lastly, some code has been refactored to make it cleaner and easier to manage on the backend
…ironments The docker-compose.dev.yml and docker-compose.prod.yml files have been updated to include new services for MongoDB and RabbitMQ. These services are necessary for the backend to function properly. Additionally, volumes have been added to persist data for MongoDB and RabbitMQ. This update improves the development and production environments by providing the required dependencies.
…endpoints The code changes introduce the ability to filter results in the get-notifications and get-users endpoints. This allows users to retrieve specific notifications and users based on certain criteria. The changes include adding new fields to the QueryInput struct and updating the FilterCollectionWithProjection function to handle the filtering logic. This enhancement improves the flexibility and usability of the backend API.
The code changes introduce a new package called "reciever" for consuming messages. This package is used in the main.go file to start consuming messages from RabbitMQ. By separating the consuming logic into its own package, the code becomes more modular and easier to maintain. This enhancement improves the overall architecture of the backend application.
The docker-compose.dev.yml and docker-compose.prod.yml files have been updated to include new services for MongoDB and RabbitMQ. These services are necessary for the backend to function properly. Additionally, volumes have been added to persist data for MongoDB and RabbitMQ. This update improves the development and production environments by providing the required dependencies.
waveyboym
added
type: documentation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #214 +/- ##
===========================================
- Coverage 71.55% 68.99% -2.56%
===========================================
Files 8 8
Lines 1174 1329 +155
===========================================
+ Hits 840 917 +77
- Misses 297 374 +77
- Partials 37 38 +1 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pr introduces some notification logic for the backend
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: