| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Change LGTM, just some comments on testing.
final interopType = getCoreInteropType(onType.nonTypeParameterBound);nit: This support the legacy `@staticInterop` types as well. Maybe worth adding a test where the extension is on a type parameter that is bound to a `@staticInterop` type as well?
V extends JSObjectMaybe use a user-defined extension type here to test with as the type parameter bound? Like `ExtensionType` in tests/lib/js/static_interop_test/extension_type/external_extension_member_test.dart?
extension SelfReferenceExtension<T extends JSObject> on T {
external T? get selfReference;
}
extension ChainedSelfReferenceExtension<
T extends U,
U extends V,
V extends JSObject
>
on T {
external T? get chainedSelfReference;
}Consider putting these in tests/lib/js/static_interop_test/extension_type/external_extension_member_test.dart instead and use this test just for a type parameter bound to a `@staticInterop` type test instead.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
final interopType = getCoreInteropType(onType.nonTypeParameterBound);nit: This support the legacy `@staticInterop` types as well. Maybe worth adding a test where the extension is on a type parameter that is bound to a `@staticInterop` type as well?
Done
Maybe use a user-defined extension type here to test with as the type parameter bound? Like `ExtensionType` in tests/lib/js/static_interop_test/extension_type/external_extension_member_test.dart?
Done
extension SelfReferenceExtension<T extends JSObject> on T {
external T? get selfReference;
}
extension ChainedSelfReferenceExtension<
T extends U,
U extends V,
V extends JSObject
>
on T {
external T? get chainedSelfReference;
}Consider putting these in tests/lib/js/static_interop_test/extension_type/external_extension_member_test.dart instead and use this test just for a type parameter bound to a `@staticInterop` type test instead.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
{Very tiny nit, but do we need the extra scope? Pro is that it breaks apart the multiple tests better but con is that it's inconsistent with the rest of the test.
extensionObj as JSObject;nit: Don't need the cast because the type implements `JSObject`.
var obj = StaticInteropClass();This doesn't exist in the JS `eval` code, so I expect this test will fail.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Very tiny nit, but do we need the extra scope? Pro is that it breaks apart the multiple tests better but con is that it's inconsistent with the rest of the test.
Done
nit: Don't need the cast because the type implements `JSObject`.
Done
This doesn't exist in the JS `eval` code, so I expect this test will fail.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |