You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the important pieces that wasm-bindgen provides is the generated typescript declaration file that describes the public API of the generated bindings. If I understand correctly,when using ducktor in a public facing API, the types will just show up as JsValues and all type information will be lost. So even though you can pass any object with the same fields, you would not get typechecking for those objects.
The text was updated successfully, but these errors were encountered:
One of the important pieces that wasm-bindgen provides is the generated typescript declaration file that describes the public API of the generated bindings. If I understand correctly,when using ducktor in a public facing API, the types will just show up as JsValues and all type information will be lost. So even though you can pass any object with the same fields, you would not get typechecking for those objects.
The text was updated successfully, but these errors were encountered: