Deprecate BindingBase.window#120998
Conversation
|
@pdblasi-google This is my suggestion for the deprecation message on |
0f2847f to
f66fc71
Compare
d109cfc to
f0e08e3
Compare
There was a problem hiding this comment.
Consider:
| /// If a [BuildContext] is available, consider looking up the current | |
| /// [FlutterView] associated with that context via [View.of]. It gives access | |
| /// If a [BuildContext] is available, you can get the context's | |
| /// current [FlutterView] via [View.of]. It gives access |
I don't feel strongly about this
There was a problem hiding this comment.
I am gonna leave this as-is since our style guide doesn't like to use the word "you": https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#use-the-passive-voice-recommend-do-not-require-never-say-things-are-simple
There was a problem hiding this comment.
I prefer the language you use below in the See also section:
| /// to the same functionality as this deprecated property. However, some | |
| /// functionality has moved to the [PlatformDispatcher], which should be | |
| /// to the same functionality as this deprecated property. The | |
| /// platform-specific functionality has moved .... |
I don't feel strongly about this
There was a problem hiding this comment.
Consider simpler language for non-native speakers:
| /// [platformDispatcher] exposed by this binding can be consulted directly for | |
| /// [platformDispatcher] exposed by this binding can be used directly for |
f0e08e3 to
4d23cf2
Compare
4d23cf2 to
c107892
Compare
Part of #116929.
Migration Guide: flutter/website#8283
Also adds ignores required for flutter/engine#39302.
To be submitted after deprecations for
flutter_test.