There are ways to make the libraries more readable and idiomatic while staying within the bounds of the repo style guide.

Since the primary readers of Flutter code are Flutter app developers, and since all Flutter apps created since 2.3.0 use flutter_lints, we should too, when able.

• curly_braces_in_flow_control_structures
  • Use curly_braces_in_flow_control_structures for material #104499
  • Use curly_braces_in_flow_control_structures for animations, cupertino #104612
  • Use curly_braces_in_flow_control_structures for widgets #104609
  • Use curly_braces_in_flow_control_structures for foundation, gestures, painting, physics #104610
  • Use curly_braces_in_flow_control_structures for rendering #104611
  • Use curly_braces_in_flow_control_structures for services, scheduler, semantics #104616
  • Use curly_braces_in_flow_control_structures for non-flutter packages #104629
  • Use curly_braces_in_flow_control_structures for sample code #104617
  • Use curly_braces_in_flow_control_structures for gen_defaults #104921
  • Turn on curly_braces_in_flow_control_structures for developer-facing code #105113