Baseflow / Baseflow/flutter-geolocator

[Enhancement proposal]: Return Notification ID (Android)

Open
#1,562 0 comments 0 reactions 0 assignees View on GitHub
refactor type: enhancement
Dominant language
Dart
Stars
1.3k
Forks
803
Avg merge
8h 16m
Merged PRs (30d)
1

Description

### Please check the following before submitting a new issue.

- [X] I have searched the [existing issues](https://github.com/baseflow/flutter-geolocator/issues).
- [X] I have carefully [read the documentation](https://github.com/baseflow/flutter-geolocator/blob/main/geolocator/README.md) and verified I have added the required platform specific configuration.

### Please select affected platform(s)

- [X] Android
- [ ] iOS
- [ ] Linux
- [ ] macOS
- [ ] Web
- [ ] Windows

### Proposal

Currently only the channel-name can be set. If the notification needs to be updated, the notification ID is required.

### Pitch

Is it possible to return (or specify) the notification ID when creating `ForegroundNotificationConfig` ?

Contributor guide

Open the contributing guide

Research direction

Start by locating ForegroundNotificationConfig and tracing how Android foreground notifications are created and exposed through the plugin. Determine whether the change should return or accept a notification ID, then identify the existing tests or platform entry points that would verify the ID can be used for updates; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, dart
Domain
mobile-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.