Skip to content

docs: apply final review suggestions to dot shorthands guide#13255

Closed
lamek wants to merge 1 commit intoflutter:clean-dot-shorthandsfrom
lamek:clean-dot-shorthands
Closed

docs: apply final review suggestions to dot shorthands guide#13255
lamek wants to merge 1 commit intoflutter:clean-dot-shorthandsfrom
lamek:clean-dot-shorthands

Conversation

@lamek
Copy link
Copy Markdown
Contributor

@lamek lamek commented Apr 7, 2026

Adds a guide on Dart shorthands to the flutter docs.

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.

Clone of #13180. Ran into some Git issues locally.

@lamek lamek requested review from a team and sfshaza2 as code owners April 7, 2026 13:22
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for Dart dot shorthands by refining the explanation of context types and simplifying the code examples. A grammatical error was identified in the section regarding enums where 'is expects' should be corrected to 'expects'.

### Example: enums

When a property expects an `enum`, such as `mainAxisAlignment`, you can omit the
When the context type is expects an `enum`, such as `mainAxisAlignment`, you can omit the
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase "is expects" is grammatically incorrect. It should be "expects" or "is an".

Suggested change
When the context type is expects an `enum`, such as `mainAxisAlignment`, you can omit the
When the context type expects an enum, such as mainAxisAlignment, you can omit the

@lamek lamek closed this Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant