Format all SCSS, Markdown, yaml, HTML files

[guidezpl]

Description of what this PR is changing or adding, and why: Auto-format all SCSS, Markdown, yaml, HTML files, using the default VS Code formatter and default formatting options, per #12501 (comment).

Issues fixed by this PR (if any): #12498

PRs or commits this PR depends on (if any):

Presubmit checklist

• If you are unwilling, or unable, to sign the CLA, even for a tiny, one-word PR, please file an issue instead of a PR.
• If this PR is not meant to land until a future stable release, mark it as draft with an explanation.
• This PR follows the Google Developer Documentation Style Guidelines—for example, it doesn't use i.e. or e.g., and it avoids I and we (first-person pronouns).
• This PR uses semantic line breaks
  of 80 characters or fewer.

[gemini-code-assist]

Summary of Changes

Hello @guidezpl, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is dedicated to improving code consistency and readability by applying automated formatting to a wide range of file types, including SCSS, Markdown, YAML, and HTML. The changes are purely stylistic, aiming to standardize the codebase's appearance according to default VS Code formatting rules, which helps in reducing cognitive load for developers and streamlines future contributions.

Highlights

• Automated Formatting: This pull request introduces automated formatting for SCSS, Markdown, YAML, and HTML files across the repository, ensuring consistent code style.
• VS Code Default Formatter: The formatting adheres to the default settings of the VS Code formatter, standardizing the codebase without custom configurations.
• Whitespace and Readability Improvements: Changes primarily involve adjusting whitespace, adding/removing newlines, correcting indentation, and re-wrapping lines to enhance readability and maintainability of various file types.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request focuses on auto-formatting various file types (SCSS, Markdown, YAML, HTML) to improve code consistency and readability. The changes primarily involve removing unnecessary newlines and adjusting spacing, aligning the code with standard formatting conventions. I have provided review comments for some of the changes, focusing on areas where the formatting could be further improved or where inconsistencies were introduced.

[flutter-website-bot]

Visit the preview URL for this PR (updated for commit 304e704):

https://flutter-docs-prod--pr12609-formatting-fy5keo21.web.app

[parlough]

Thanks for doing this!

Once we have a chance, we can investigate a good way to automate this without requiring too much extra contributor setup.