refactor: federated plugin — Melos monorepo + flutter_pdfview_platform_interface

[endigo]

Stacks on #345 — base is migrate/kotlin-swift, so review that one first.

Turns the repository into a federated plugin, then fixes two toolchain warnings Flutter 3.44 prints on every build.

No public API change. PDFView, PDFViewController, every callback and enum keep the same names, semantics and import path. The native code, the platform-view type and the method-channel protocol are untouched, so existing native implementations keep working — and the entire 1.5.0-beta.10 Dart suite passes unmodified.

What changed

1. Melos + pub workspaces monorepo (7ff312b)

The published package moved to packages/flutter_pdfview/. The root is now a workspace declaring members and inlining the melos config.

pubspec.yaml              workspace root + melos scripts
pubspec.lock              the single lockfile; members must not carry one
packages/
  flutter_pdfview/                     app-facing, keeps android/ + ios/
  flutter_pdfview_platform_interface/  new

melos run analyze | test | test:android | format | publish:dry-run cover every package. publish.yml now sets working-directory: packages/flutter_pdfview, and scripts/ was repointed.

2. Extract flutter_pdfview_platform_interface (2ebe1fd)

Type	Role
FlutterPdfViewPlatform	What implementations extend; buildView returns the hosting widget
PdfViewPlatformController	Per-view ops — paging, zoom, scroll, screenshot, unlock
PdfViewSettings	Wire format + updatesMap, the diff that updates a live view instead of remounting
PdfViewCreationParams / PdfViewCallbacks	Creation payload and event bundle
MethodChannelFlutterPdfView	Default impl: UiKitView, PlatformViewLink + initExpensiveAndroidView, unsupported-platform Text

PDFViewController is now a thin wrapper over PdfViewPlatformController. Adding a platform (web #65, macOS #84, Windows #165) no longer means touching the app-facing package.

The shared value types moved into the interface and are re-exported from package:flutter_pdfview/flutter_pdfview.dart, so app code needs no changes.

3. Toolchain fixes (f16dc7b)

iOS — Package.swift declared dependencies: []. Flutter 3.44+ requires plugins to declare FlutterFramework explicitly instead of inheriting the embedder from the generated Runner package. Warning is gone. The ObjC shim only imports Foundation, so it deliberately does not take the dependency.

Android — AGP 9 compiles Kotlin itself and Flutter fails the build of any app whose plugins also apply KGP, so this plugin would have broken apps on future Flutter releases. Removing KGP unconditionally would break everyone on AGP 8, which this plugin still supports (pubspec requires only Flutter ≥ 3.32), so it is now AGP-gated:

def agpMajor = com.android.Version.ANDROID_GRADLE_PLUGIN_VERSION.tokenize('.')[0] as int
if (agpMajor < 9) {
    apply plugin: 'kotlin-android'
}

with kotlinOptions replaced by kotlin { compilerOptions { jvmTarget } }, which both toolchains understand.

Verification

Check	Result
App-facing Dart tests	127 pass, unmodified
Platform-interface tests	38 pass (new)
Android unit tests	123 tests, 0 failures, 0 errors
iOS integration tests (simulator)	11/11 against real PDFKit
Example Android APK	builds
Example iOS build (SPM)	builds, no FlutterFramework warning
CocoaPods pod lib lint	passes
melos bootstrap / analyze / format-check	clean
pub publish --dry-run	interface 0 warnings

The AGP 9 path was verified rather than assumed, by temporarily moving the example to AGP 9.3.1 + Gradle 9.5.0 + android.builtInKotlin=true. That caught a real bug — the naive form from the migration guide fails, because the kotlin { } extension does not exist under AGP 9 unless built-in Kotlin is enabled. With the fix, flutter_pdfview evaluates cleanly and appears in no failure. The example app config was restored afterwards and is unchanged in this PR.

Reviewer notes

• Release order is now load-bearing. flutter_pdfview_platform_interface must be published before flutter_pdfview, which declares flutter_pdfview_platform_interface: ^1.0.0. Inside the workspace it resolves locally; on pub.dev it will not resolve until the interface is up.
• Callback semantics. Callbacks used to be a live read of the widget; they are now a PdfViewCallbacks snapshot, re-pointed both at controller construction and on every widget update. Without that, a widget rebuilt before the platform view finished creating would dispatch into stale closures.
• The KGP warning still shows on AGP 8, by design — the plugin genuinely still applies KGP there. It disappears once an app is on AGP 9 with built-in Kotlin. Removing it unconditionally would mean raising the floor to Flutter 3.47+, which is a breaking change and a maintainer decision.
• flutter_pdfview bumped to 1.5.0-beta.11; the interface starts at 1.0.0.

Not covered

• Android integration tests were not run — a hung emulator held the AVD lock on the machine this was built on. iOS integration tests did run.
• Under AGP 9 the example build still fails, but on packages outside this repo that have not migrated: Flutter's own integration_test, and jni.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XKmmG2v9eJSWFDLy6mRe8F

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0de9cf07-f301-4347-af3a-84cb3deb0641

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}