fix: incorrect fvm spawn example

[GChanathip]

the command should be fvm spawn x.x.x build not fvm spawn x.x.x flutter build

Summary by CodeRabbit

• Documentation
  • Simplified command examples in the guides by removing redundant references.
  • Adjusted examples for building and testing commands for clarity.
  • Improved formatting for command examples to enhance readability.

[vercel]

@GChanathip is attempting to deploy a commit to the FlutterTools Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The documentation update revises command examples in the basic commands guide. The changes remove the explicit "flutter" keyword from the fvm spawn command examples for building and testing, presenting a more concise syntax. Additionally, the example for fvm flavor has been updated to ensure proper formatting by appending a newline at the end. These are solely changes to the documentation with no modifications to underlying functionality or exported entities.

Changes

File(s)	Change Summary
docs/.../basic-commands.mdx	Removed explicit flutter prefix in fvm spawn command examples; added newline in fvm flavor example formatting.

Poem

I'm a rabbit, hopping with delight,
Commands streamlined, shining ever so bright,
No "flutter" cluttering my path in sight,
Docs now dance with clarity in the light,
Hoppity cheers for changes done just right!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 863c977 and 40c7749.

📒 Files selected for processing (1)

• docs/pages/documentation/guides/basic-commands.mdx (2 hunks)

🔇 Additional comments (3)

docs/pages/documentation/guides/basic-commands.mdx (3)

271-272: Update the fvm spawn command example to remove the redundant flutter keyword.

The revised command (fvm spawn 2.5.0 build) now correctly reflects the intended usage as outlined in the PR objectives, simplifying the syntax and reducing confusion.

---

278-279: Correct the test command example for fvm spawn.

The updated example (fvm spawn 2.2.3 test) omits the unnecessary flutter keyword, aligning the documentation with the correct syntax.

---

361-362: Verify the formatting for the flavor command example.

A newline has been appended at the end of the fvm flavor staging flutter test command to ensure proper formatting. Please confirm that this formatting change meets the documentation style guidelines.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.