Skip to content

Conversation

loic-sharma
Copy link
Member

@loic-sharma loic-sharma commented Aug 11, 2025

Bubble up that flutter config --help explains what each flag controls.

cc @vashworth @matanlurey

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.

@flutter-website-bot
Copy link
Collaborator

flutter-website-bot commented Aug 11, 2025

Visit the preview URL for this PR (updated for commit 95da1c9):

https://flutter-docs-prod--pr12293-pubspec-config-knem15y3.web.app

@matanlurey
Copy link
Contributor

My concern with this change is that it is likely to go out of date with flutter config --help. I think it could be valuable to list flags we expect to stick around for long periods of time, or perhaps to talk about we have a few different categories of flags as you listed, but otherwise I'd say away with trying to duplicate the command line documentation.

@loic-sharma loic-sharma changed the title Document flags that can be enabled in .pubspec Update instructions on how to discover flags that can be configure in .pubspec Aug 11, 2025
@loic-sharma loic-sharma changed the title Update instructions on how to discover flags that can be configure in .pubspec Recommend flutter config --help for an explanation of each feature flag Aug 11, 2025
@loic-sharma
Copy link
Member Author

@matanlurey and I discussed offline. Instead of explaining each flag here, I switched to recommending flutter config --help to get an explanation of flags.

@loic-sharma loic-sharma marked this pull request as ready for review August 22, 2025 21:59
@loic-sharma loic-sharma requested review from sfshaza2, antfitch, parlough and a team as code owners August 22, 2025 21:59
Copy link
Contributor

@sfshaza2 sfshaza2 left a comment

Choose a reason for hiding this comment

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

lgtm. Thanks, @loic-sharma, for adding this info. And thanks, @matanlurey, for making the docs more robust over time.

@sfshaza2 sfshaza2 merged commit 214c839 into flutter:main Aug 25, 2025
9 checks passed
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.

4 participants