Conversation
📝 WalkthroughSummary by CodeRabbit
Summary by CodeRabbit
WalkthroughThe changes transition the project from a development phase to a stable release by updating version identifiers, simplifying the changelog, refining notification payload handling in the Android plugin, and streamlining the example app's initialization, state management, and UI. The intent extras filtering logic is enhanced, and the example app's structure is modernized. Changes
Sequence Diagram(s)sequenceDiagram
participant AppMain as main()
participant PntaFlutter as PntaFlutter SDK
participant HomePage as HomePage Widget
AppMain->>PntaFlutter: initialize(projectId, userMetadata, config)
AppMain->>HomePage: runApp(MyApp)
HomePage->>PntaFlutter: Listen for notifications
PntaFlutter-->>HomePage: onNotificationReceived(payload)
HomePage->>HomePage: Update _lastNotification
HomePage->>UI: Display notification payload and status
Possibly related PRs
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (2)
CHANGELOG.md (1)
1-3: Consider preserving dev-build history
Stripping pre-release entries makes the file concise, but you lose a traceable audit of changes between dev builds. You may want to append rather than replace to retain that history.android/src/main/kotlin/io/pnta/pnta_flutter/PntaFlutterPlugin.kt (1)
137-139: Broaden numeric type handling
Instead of enumerating every primitive, treating allNumbersub-classes in one clause is safer and future-proof:- when (value) { - is String, is Int, is Boolean, is Double, is Float, is Long -> payload[key] = value + when (value) { + is String, is Boolean -> payload[key] = value + is Number -> payload[key] = value
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
example/pubspec.lockis excluded by!**/*.lock
📒 Files selected for processing (5)
CHANGELOG.md(1 hunks)android/src/main/kotlin/io/pnta/pnta_flutter/PntaFlutterPlugin.kt(2 hunks)example/lib/main.dart(1 hunks)lib/src/version.dart(1 hunks)pubspec.yaml(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: CI
example/lib/main.dart
[error] 1-1: dart format check failed. The file was changed by the formatter, indicating formatting issues. Run 'dart format .' to fix code style.
🔇 Additional comments (3)
lib/src/version.dart (1)
3-3: Version bump looks correct and consistent
The constant now matches the stable1.0.0release. No other action required.pubspec.yaml (1)
3-3: Remember to publish the tag after changingversion:
Everything else in the manifest remains untouched, so a straightflutter pub publish --dry-runshould succeed.android/src/main/kotlin/io/pnta/pnta_flutter/PntaFlutterPlugin.kt (1)
145-145: Confirm intent propagation policy
Returningfalselets other plugins / the activity keep handling the intent. Double-check that no downstream component relies on seeing the raw FCM extras (now stripped) before deciding to continue.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
README.md (1)
298-300: Enhance link to example app
Consider making theexample/folder reference a clickable relative link (e.g.,[example/](./example/)or linking directly toexample/README.md) to improve discoverability and navigation.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(2 hunks)
🔇 Additional comments (1)
README.md (1)
20-20: ToC entry update looks good
The newExampleentry correctly replaces the old inline sections and aligns with the consolidated Example section below.
1 participant
Filter FCM metadata from notification tap payloads, clean up example app, and bump to v1.0.0 stable release.