-
Notifications
You must be signed in to change notification settings - Fork 31
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(notifications_push_repository): Init #2482
Conversation
Also makes it possible to implement #213 later. |
d3ef216
to
7d16bc0
Compare
Should we land the repository and the migration changes in separate PRs? Both commits are already huge to begin with. |
Hm if we only have 2 PRs I'd say just merge the repository into main and then later the refactor. |
7d16bc0
to
e8880db
Compare
I removed the framework commit and pushed it to a separate branch. Once merged I'll open a new PR for that. |
e8880db
to
fad21d1
Compare
I rebased this, but while testing I found an error with the push subscription registration. |
fad21d1
to
7ec5abb
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2482 +/- ##
==========================================
+ Coverage 28.56% 28.66% +0.10%
==========================================
Files 359 366 +7
Lines 136078 136296 +218
==========================================
+ Hits 38865 39076 +211
- Misses 97213 97220 +7
*This pull request uses carry forward flags. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work.
I'm not a big fan of the code style in the repo.
Many methods in there do not take any parameters and rely on the global state of the repo. I've already outlined most of my concerns, and maybe fixing them is enough.
.../neon_framework/packages/notifications_push_repository/lib/src/models/push_notification.dart
Outdated
Show resolved
Hide resolved
...eon_framework/packages/notifications_push_repository/lib/src/notifications_push_storage.dart
Outdated
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
packages/neon_framework/packages/notifications_push_repository/lib/src/utils/encryption.dart
Show resolved
Hide resolved
..._framework/packages/notifications_push_repository/lib/src/notifications_push_repository.dart
Outdated
Show resolved
Hide resolved
7ec5abb
to
4d72c86
Compare
…Store Signed-off-by: provokateurin <[email protected]>
Signed-off-by: provokateurin <[email protected]>
4d72c86
to
80071e4
Compare
Signed-off-by: provokateurin <[email protected]>
80071e4
to
29f6a4b
Compare
#577
Depends on #2407 (due to an ugly cyclic dependency)
The framework part can probably be improved, but I just wanted to put out the repository so it can get reviewed.
The repository now handles all possible things that could go wrong and retries registering at UnifiedPush or Nextcloud if necessary. This should make push notifications super reliable and usable.