1. 14 Jan, 2024 1 commit
  2. 13 Nov, 2023 1 commit
    • huycozy's avatar
      Update DraggableScrollableSheet docs to reflect API change (#136471) · 61c007a3
      huycozy authored
      ### Description
      
      This PR intends to update `DraggableScrollableSheet` docs for Web and Desktop platforms. On these platforms, the vertical dragging gesture does not provide natural behavior similar to other desktop applications. 
      
      By adding a note before the sample code so users are aware that the sample code will not work as expected on Desktop and Web. Also, refer to the instructions if they still want to implement it on these platforms.
      
      ### Related issue
      
      Fixes https://github.com/flutter/flutter/issues/111372
      61c007a3
  3. 22 Oct, 2023 1 commit
    • Todd Volkert's avatar
      Add timeline events for post frame callbacks (#136435) · cb9a3f69
      Todd Volkert authored
      Before this change, long-running post-frame callbacks wouldn't show up in the timeline at all.  This adds a timeline event for post-frame callbacks, with a debug flag that will add timeline events for each individual callback.
      
      #testexempt -- we have no way to test calls to the timeline.
      cb9a3f69
  4. 30 Sep, 2023 1 commit
  5. 20 Sep, 2023 1 commit
    • Greg Spencer's avatar
      Remove 'must be non-null' and 'must not be null' comments in widgets library (#134992) · 6e5134b0
      Greg Spencer authored
      ## Description
      
      This removes all of the comments that are of the form "so-and-so (must not be null|can ?not be null|must be non-null)" from the cases where those values are defines as non-nullable values.
      
      This PR removes them from the widgets library.
      
      This was done by hand, since it really didn't lend itself to scripting, so it needs to be more than just spot-checked, I think. I was careful to leave any comment that referred to parameters that were nullable, but I may have missed some.
      
      In addition to being no longer relevant after null safety has been made the default, these comments were largely fragile, in that it was easy for them to get out of date, and not be accurate anymore anyhow.
      
      This did create a number of constructor comments which basically say "Creates a [Foo].", but I don't really know how to avoid that in a large scale change, since there's not much you can really say in a lot of cases.  I think we might consider some leniency for constructors to the "Comment must be meaningful" style guidance (which we de facto have already, since there are a bunch of these).
      
      ## Related PRs
      - https://github.com/flutter/flutter/pull/134984
      - https://github.com/flutter/flutter/pull/134991
      - https://github.com/flutter/flutter/pull/134993
      - https://github.com/flutter/flutter/pull/134994
      
      ## Tests
       - Documentation only change.
      6e5134b0
  6. 19 Sep, 2023 1 commit
  7. 18 Sep, 2023 2 commits
  8. 08 Sep, 2023 1 commit
  9. 06 Sep, 2023 1 commit
  10. 31 Aug, 2023 1 commit
  11. 22 May, 2023 1 commit
  12. 29 Apr, 2023 1 commit
  13. 12 Apr, 2023 1 commit
  14. 17 Feb, 2023 1 commit
  15. 25 Jan, 2023 1 commit
  16. 24 Jan, 2023 1 commit
  17. 03 Jan, 2023 1 commit
  18. 27 Dec, 2022 1 commit
  19. 22 Dec, 2022 1 commit
  20. 28 Oct, 2022 1 commit
  21. 29 Sep, 2022 1 commit
  22. 28 Sep, 2022 1 commit
  23. 23 Sep, 2022 1 commit
  24. 16 Sep, 2022 1 commit
  25. 13 Sep, 2022 1 commit
  26. 02 Sep, 2022 1 commit
  27. 09 Aug, 2022 1 commit
  28. 25 Jul, 2022 1 commit
  29. 12 Jul, 2022 1 commit
  30. 30 Jun, 2022 1 commit
  31. 25 May, 2022 1 commit
  32. 18 May, 2022 1 commit
  33. 17 May, 2022 1 commit
  34. 05 May, 2022 1 commit
  35. 27 Apr, 2022 1 commit
  36. 26 Apr, 2022 1 commit
  37. 14 Apr, 2022 2 commits
  38. 08 Apr, 2022 1 commit