Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Implement a "warning" log level, and add --fatal-warnings to the tool #91325

Closed
@gspencergoog

Description

@gspencergoog

Description

In order to allow us to check in CI that nothing untoward happened during a run, it would be nice to have a --fatal-warnings flag to the flutter tool that would change the exit code to a non-zero exit if there had been any warnings printed to the logger during that run.

This would allow things like outdated runner deprecations warnings to break the build so that we could be sure that things were up to date, and not causing warnings that are unheeded in the repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectc: new featureNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions