1. 15 Dec, 2023 1 commit
  2. 13 Sep, 2023 1 commit
  3. 14 Apr, 2022 1 commit
  4. 21 Apr, 2021 1 commit
  5. 15 Oct, 2020 1 commit
  6. 11 Jun, 2020 1 commit
  7. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  8. 26 Jul, 2019 1 commit
  9. 12 Sep, 2018 1 commit
  10. 19 Jun, 2018 1 commit
  11. 21 Apr, 2017 1 commit
  12. 11 Apr, 2017 1 commit
    • xster's avatar
      Rename State.config to widget everywhere (#9273) · 89a7fdfc
      xster authored
      Rename State.config to State.widget
      Rename State.didUpdateConfig to State.didUpdateWidget
      Renamed all State subclasses' local variables named config to something else
      89a7fdfc
  13. 04 Mar, 2017 1 commit
  14. 07 Nov, 2016 1 commit
  15. 26 Sep, 2016 1 commit
    • Ian Hickson's avatar
      LayoutBuilder + GlobalKey + setState assert (#6068) · 78c74116
      Ian Hickson authored
      This silences an assertion that fired when reparenting a widget with a
      global key inside a LayoutBuilder callback when that callback also
      happened to call setState (directly or indirectly) on that widget.
      
      Normally such setStates are considered ok since we know we haven't
      cleaned that subtree yet, but we were not correctly handling the case
      where the list needed resorting in that situation.
      78c74116