docs(flutter): fix stale plugin name in pubspec dependency snippet#719
Merged
Conversation
Section 2-1 of the Flutter setup guide told users to add a `mopro_flutter_plugin` dependency at `path: ./mopro_flutter_plugin`, but the folder copied in step 1 (and used everywhere else in the page, in the imports, and by the Mopro CLI scaffolding) is `mopro_flutter_bindings`. This leftover from the old plugin-based flow would fail to resolve. Update the snippet to `mopro_flutter_bindings` / `path: ./mopro_flutter_bindings`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Smkp7CuhA7VjLwriicL12a
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Flutter setup documentation updates its ChangesFlutter setup
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Deploying mopro with
|
| Latest commit: |
9fc1a45
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://03a8e8a5.mopro.pages.dev |
| Branch Preview URL: | https://claude-mopro-flutter-binding.mopro.pages.dev |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
mopro | 9fc1a45 | Jul 11 2026, 03:41 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Section 2-1 of the Flutter setup guide (
docs/docs/setup/flutter-setup.md) tells users to add apubspec.yamldependency namedmopro_flutter_pluginatpath: ./mopro_flutter_plugin:But the folder users actually copy in step 1 — and that's referenced everywhere else on the page — is
mopro_flutter_bindings:mopro_flutter_bindingsfolderpackage:mopro_flutter_bindings/...mopro_flutter_bindingsThe
mopro_flutter_pluginname is a leftover from the old, deprecated plugin-based flow. Since the Dart package is namedmopro_flutter_bindings, this dependency entry would not resolve. The Mopro CLI that scaffolds these apps also writespath: ./mopro_flutter_bindings(cli/src/create/flutter.rs), confirming the intended value.Fix
Update the section 2-1 snippet to match:
This was the only occurrence of
mopro_flutter_pluginin the current docs. The versioned snapshots (versioned_docs/version-0.1,version-0.2) legitimately usemopro_flutter_pluginthroughout for their era and are intentionally left untouched.🤖 Generated with Claude Code
https://claude.ai/code/session_01Smkp7CuhA7VjLwriicL12a
Generated by Claude Code
Summary by CodeRabbit
mopro_flutter_bindingsdependency in thepubspec.yamlexample.