New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we be using the internal Since
annotation for new features?
#37127
Comments
Since
annotation for new features?
CC @mit-mit |
Ditto for |
True, we should use it. If for nothing else, then for documentation. For breaking changes, it's not always possible to find a place to put the annotation, but incremental changes should be doable. |
* HttpClientResponse.compressionState * HttpClientResponseCompressionState Bug: #37127 Change-Id: I1823156bc3545b87293dfa61471e8d5c97013cdc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/104483 Commit-Queue: Kevin Moore <kevmoo@google.com> Reviewed-by: Kevin Moore <kevmoo@google.com>
|
For the record, new features should be releases in minor version increments, so the next release where new features are released will be If we release a |
I think the sdk version doesn't follow strict semver, and won't always rev the minor version even when there are api additions (reving the sdk version is more of a product decision than a semver one). |
Addresses some parts of #37127 Bug: http://dartbug.com/37127 Change-Id: Ia3a98e5764a16529331b2ba5613096d27061cab0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/104763 Commit-Queue: Lasse R.H. Nielsen <lrn@google.com> Reviewed-by: Todd Volkert <tvolkert@google.com> Reviewed-by: Jonas Termansen <sortie@google.com>
We should generally use |
sdk/sdk/lib/internal/internal.dart
Lines 200 to 204 in a25f927
aa2ce7c just landed
HttpClientResponse. compressionState
andHttpClientResponseCompressionState
Should these be annotated w/
Since
? @lrhn @turnidge @zandersoShould we look to get Analyzer to support
Since
so it's useful for end users? @stereotype441 @devoncarew @bwilkersonThe text was updated successfully, but these errors were encountered: