Skip to content

0.10.0

Choose a tag to compare

View all tags
@MaxDesiatov MaxDesiatov released this 21 Jan 17:19
· 800 commits to main since this release
0.10.0
ebd9ca0
This commit was signed with the committer’s verified signature. The key has expired.
MaxDesiatov Max Desiatov
GPG key ID: FE08EBF9CF58CBA2
Expired
Verified
Learn about vigilant mode.

This release contains multiple breaking changes in preparation for enabling async/await, when this feature is available in a stable SwiftWasm release. Namely:

  • JSClosure.init(_ body: @escaping ([JSValue]) -> ()) overload is deprecated to simplify type checking. Its presence requires explicit type signatures at the place of use. It will be removed in a future version of JavaScriptKit.
  • JSClosure is no longer a subclass of JSFunction. These classes are not related enough to keep them in the same class hierarchy. As a result, you can no longer call JSClosure objects directly from Swift. Call wrapped closures directly instead.
  • Introduced JSOneshotClosure for closures that are going to be called only once. You don't need to manage references to these closures manually, as opposed to JSClosure. However, they can only be called a single time from the JS side. Subsequent invocation attempts will raise a fatal error on the Swift side.
  • Removed generic parameters on JSPromise, now both success and failure values are always assumed to be of JSValue type. This also significantly simplifies type checking and allows callers to fully control type casting if needed.

Closed issues:

  • DOMKit? (#21)

Merged pull requests:

Assets 2
Loading