mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-05-11 21:37:16 +00:00

History

Alex Crichton 01a52233d3 Support [NoInterfaceObject] in web-sys

This commit enables `[NoInterfaceObject]` annotated interfaces in
`web-sys`. The `NoInterfaceObject` attribute means that there's not
actually a JS class for the object, but all of its properties and such
can still be accessed structually and invoked. This should help provide
more bindings for some more common types on the web!

Note that this builds on recent features to ensure that `dyn_into` and
friends always fail for `NoInterfaceObject` objects because they don't
actually have a class.

Closes #893
Closes #1257
Closes #1315

2019-04-15 10:36:01 -07:00

src

Migrate all crates to the 2018 edition

2019-03-26 08:10:53 -07:00

tests/wasm

Generate r#async method names in web-sys

2019-03-26 08:51:46 -07:00

webidls

impl OptionFromWasmAbi and OptionIntoWasmAbi for ImportEnum, enable RTCRtpTransceiver.webidl, add add rtc_rtp_transceiver_direction test

2019-03-14 12:15:02 -06:00

build.rs

Run rustfmt over everything

2018-11-27 12:07:59 -08:00

Cargo.toml

Support [NoInterfaceObject] in web-sys

2019-04-15 10:36:01 -07:00

README.md

Simply remove the web-sys bindings 'tested' list

2019-01-10 19:06:11 +01:00

README.md

`web-sys`

Raw bindings to Web APIs for projects using wasm-bindgen.

Crate features

This crate by default contains very little when compiled as almost all of its exposed APIs are gated by Cargo features. The exhaustive list of features can be found in crates/web-sys/Cargo.toml, but the rule of thumb for web-sys is that each type has its own cargo feature (named after the type). Using an API requires enabling the features for all types used in the API, and APIs should mention in the documentation what features they require.