Skip to content

Add parseable output for flutter doctor #10621

@DanTup

Description

@DanTup

I thought I'd discussed this with someone before, but can't find it anywhere.. It'd be nice if an IDE can execute flutter doctor and provide info to the user when there are problems.

The current output isn't too bad for parsing, but it could be fragile if there are changes or if it becomes interactive and starts expecting input.

It'd be good to have a new switch (eg. --machine) that'll give output in a consistent format. Another possibility is adding it as a command to flutter daemon, however I don't know if the daemon can actually run if there are missing pre-requisites, so maybe that's not a good idea!

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listc: new featureNothing broken; request for a new capabilityt: flutter doctorProblem related to the "flutter doctor" toolteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions