Remove the hack used to get the runtimeType without using an additional class in key.dart#178219
Conversation
runtimeType without using an additional class
|
It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
|
test-exempt: code refactor with no semantic change |
runtimeType without using an additional classruntimeType without using an additional class in key.dart
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…n additional class in `key.dart` (flutter/flutter#178219)
…onal class in `key.dart` (flutter#178219) some context : [flutter#33297](dart-lang/sdk#33297) suggested that `Type literals should support generics` which means that this would become a valid syntax `Type type = List<int>;`. the hack used here directly references to that issue : https://github.com/flutter/flutter/blob/2981516d74bc2b3307a7386e7be906602b65cf22/packages/flutter/lib/src/foundation/key.dart#L109-L120 because something like : ```dart Type type = List<int>; typedef MakeNullable<T> = T?; typedef TypeOf<T> = T; ``` was not a valid syntax at the time of writing `key.dart` since that issue is closed and those are valid syntax now , it is safe to remove this hack and use what @lrhn suggested in this [comment](dart-lang/sdk#33297 (comment)) ```dart typedef TypeOf<T> = T; ``` in other words , before: ```dart if (runtimeType == _TypeLiteral<ValueKey<T>>().type) { } class _TypeLiteral<T> { Type get type => T; } ``` after: ```dart if (runtimeType == _TypeOf<ValueKey<T>>) { } typedef TypeOf<T> = T; ``` ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: Victor Sanni <victorsanniay@gmail.com>
…onal class in `key.dart` (flutter#178219) some context : [flutter#33297](dart-lang/sdk#33297) suggested that `Type literals should support generics` which means that this would become a valid syntax `Type type = List<int>;`. the hack used here directly references to that issue : https://github.com/flutter/flutter/blob/2981516d74bc2b3307a7386e7be906602b65cf22/packages/flutter/lib/src/foundation/key.dart#L109-L120 because something like : ```dart Type type = List<int>; typedef MakeNullable<T> = T?; typedef TypeOf<T> = T; ``` was not a valid syntax at the time of writing `key.dart` since that issue is closed and those are valid syntax now , it is safe to remove this hack and use what @lrhn suggested in this [comment](dart-lang/sdk#33297 (comment)) ```dart typedef TypeOf<T> = T; ``` in other words , before: ```dart if (runtimeType == _TypeLiteral<ValueKey<T>>().type) { } class _TypeLiteral<T> { Type get type => T; } ``` after: ```dart if (runtimeType == _TypeOf<ValueKey<T>>) { } typedef TypeOf<T> = T; ``` ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: Victor Sanni <victorsanniay@gmail.com>
…onal class in `key.dart` (flutter#178219) some context : [flutter#33297](dart-lang/sdk#33297) suggested that `Type literals should support generics` which means that this would become a valid syntax `Type type = List<int>;`. the hack used here directly references to that issue : https://github.com/flutter/flutter/blob/2981516d74bc2b3307a7386e7be906602b65cf22/packages/flutter/lib/src/foundation/key.dart#L109-L120 because something like : ```dart Type type = List<int>; typedef MakeNullable<T> = T?; typedef TypeOf<T> = T; ``` was not a valid syntax at the time of writing `key.dart` since that issue is closed and those are valid syntax now , it is safe to remove this hack and use what @lrhn suggested in this [comment](dart-lang/sdk#33297 (comment)) ```dart typedef TypeOf<T> = T; ``` in other words , before: ```dart if (runtimeType == _TypeLiteral<ValueKey<T>>().type) { } class _TypeLiteral<T> { Type get type => T; } ``` after: ```dart if (runtimeType == _TypeOf<ValueKey<T>>) { } typedef TypeOf<T> = T; ``` ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: Victor Sanni <victorsanniay@gmail.com>
…n additional class in `key.dart` (flutter/flutter#178219)
some context :
#33297 suggested that
Type literals should support genericswhich means that this would become a valid syntaxType type = List<int>;.the hack used here directly references to that issue :
flutter/packages/flutter/lib/src/foundation/key.dart
Lines 109 to 120 in 2981516
because something like :
was not a valid syntax at the time of writing
key.dartsince that issue is closed and those are valid syntax now , it is safe to remove this hack and use what @lrhn suggested in this comment
in other words , before:
after:
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.