1. 09 Feb, 2024 1 commit
  2. 01 Feb, 2024 1 commit
  3. 24 Jan, 2024 1 commit
  4. 09 Jan, 2024 1 commit
  5. 02 Jan, 2024 1 commit
  6. 20 Dec, 2023 1 commit
  7. 19 Dec, 2023 1 commit
  8. 15 Dec, 2023 3 commits
  9. 06 Dec, 2023 1 commit
  10. 15 Nov, 2023 1 commit
    • Srujan Gaddam's avatar
      Pin package:web 0.4.0 (#138428) · d8ffc739
      Srujan Gaddam authored
      This version is needed so that dart:js_interop can move to extension
      types. Also adds some code to handle some breaking changes:
      
      - Body -> Response. Body was an IDL interface mixin type we exposed in
      dart:html. Going forward, users should either use Request or Response.
      - Casts to JSAny. These are temporary until we move package:web types to
      extension types. Currently, package:web types can't implement JSObject
      as JSObject will move to be an extension type itself.
      Co-authored-by: 's avatarKevin Moore <kevmoo@users.noreply.github.com>
      d8ffc739
  11. 13 Nov, 2023 1 commit
  12. 03 Nov, 2023 1 commit
  13. 01 Nov, 2023 1 commit
  14. 31 Oct, 2023 1 commit
  15. 25 Oct, 2023 1 commit
  16. 11 Oct, 2023 1 commit
  17. 29 Sep, 2023 1 commit
  18. 20 Sep, 2023 2 commits
  19. 19 Sep, 2023 1 commit
    • Greg Spencer's avatar
      Remove 'must be non-null' and 'must not be null' comments from non-framework libraries (#134994) · 4ce7fdd9
      Greg Spencer authored
      ## Description
      
      This removes all of the comments that are of the form "so-and-so must not be null" or "so-and-so must be non-null" from the cases where those values are defines as non-nullable values.
      
      This PR removes them from the library in the repo that don't have anything to do with the framework.
      
      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/134992
      - https://github.com/flutter/flutter/pull/134993
      
      ## Tests
       - Documentation only change.
      4ce7fdd9
  20. 18 Sep, 2023 1 commit
  21. 12 Sep, 2023 1 commit
  22. 16 Aug, 2023 1 commit
  23. 27 Jul, 2023 1 commit
  24. 13 Jul, 2023 1 commit
  25. 07 Jul, 2023 1 commit
  26. 15 Jun, 2023 1 commit
  27. 06 Jun, 2023 1 commit
  28. 01 Jun, 2023 1 commit
  29. 31 May, 2023 1 commit
  30. 30 May, 2023 1 commit
  31. 16 May, 2023 1 commit
  32. 09 May, 2023 1 commit
  33. 08 May, 2023 1 commit
  34. 05 May, 2023 1 commit
  35. 20 Apr, 2023 1 commit
  36. 10 Apr, 2023 1 commit
  37. 07 Apr, 2023 1 commit