-
Notifications
You must be signed in to change notification settings - Fork 30.1k
Closed as not planned
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.d: examplesSample code and demosSample code and demosd: wikiFlutter or engine wikisFlutter or engine wikisteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team
Description
Before we add more files to the template, I think we should make sure the template contains a README that documents, for each file in the template:
- What the file is for
- Why you would edit that file
- How to verify that the edits are valid
- How to test the file
The template is growing really big and it's not at all clear why some of these files are part of the user code and not just part of the framework.
We should also have a test that verifies that all files created by "flutter create" have an entry in this README file.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.d: examplesSample code and demosSample code and demosd: wikiFlutter or engine wikisFlutter or engine wikisteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team