thudugala / thudugala/Plugin.LocalNotification
Badge is bound to a notification request
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 474
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
For me it is unclear how to handle the badgeNumber in a notification request. Example: I start a request R1 with badge B1 and RepeatInterval T1. Later I start request R2 with badge B2 and RepeatInterval T2.
This will result in swapping badges B1/B2 on the app icon upon receiving a notification. And if I delete R1, I will see badge B2
Describe the solution you'd like
I guess the badgeNumber should not be bound to a request.
Describe alternatives you've considered
It should be part of LocalNotificationCenter.Current.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how badgeNumber is associated with notification requests and how LocalNotificationCenter.Current represents shared notification state. Compare the R1/R2 and deletion scenarios described in the issue, then define what behavior should remain after a request is deleted and how completion would be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100