[jsinterop] implement mocking support for static JSInterop #49351
Assignees
Labels
area-web-js
Issues related to JavaScript support for Dart Web, including DDC, dart2js, and JS interop
web-js-interop
Issues that impact all js interop
Comments
sigmundch
added
web-js-interop
37 tasks
copybara-service bot
pushed a commit
that referenced
this issue
Sep 16, 2022
Bug: #49351 Adds checks for the following cases: - Type arguments to createStaticInteropMock are correct - No missing members in implementing class - Inherited and non-overridden @staticInterop members are implemented - Dart class can implement through inheritance and mixins - Implemented members are correct subtypes of @staticInterop members - Potential extension member conflicts that are attempted to be resolved through subtyping rules Change-Id: Iacbe5846040ba7fab41459aa19be77351cf1efca Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/255761 Reviewed-by: Sigmund Cherem <[email protected]> Reviewed-by: Riley Porter <[email protected]>
copybara-service bot
pushed a commit
that referenced
this issue
Sep 16, 2022
Bug: #49351 After static checks have passed, adds functionality for a JS object literal to mock a @staticInterop class using a Dart implementation. Fields, getters, setters, and methods' names are added to the object literal, and their values are closures which call the Dart mock's members. Change-Id: Ie2ef27179eb79039d3aa28737b246c5091f4beb6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/257160 Reviewed-by: Riley Porter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JSInterop with
@staticInteroponly supports dispatching code statically and doesn't support mocking logic by implementing a Dart interface. Instead, mocks need to be implemented at the JS layer.This bug tracks progress towards support for js mocks. This includes:
The text was updated successfully, but these errors were encountered: