release: v0.7.0 — Push notifications and EAS build#60
Merged
Conversation
- Dev build (EAS development) supports push notifications - Guard was only needed for Expo Go - Permission request flow already in place
- Add googleServicesFile to app.json - Add google-services.json to gitignore - Add projectId to getExpoPushTokenAsync - Remove __DEV__ guard from token registration - Revert debug logging to silent degradation
- Event emitter with all app event constants - Notification rules — single file to change who gets what - Dispatcher — listens to events, sends notifications - expoPush utility using expo-server-sdk - complaints.ts emits events instead of direct push calls - Jest mock for expo-server-sdk - 188 tests passing
feat: push notification system
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.