This PR fixes#430 and enables full support for the
`wasm32-unknown-unknown` compilation target, making chorus the first(?)
Rust Discord-API implementation to support this target.
This PR applies the necessary patches to correctly pass (all but two)
tests when compiling for wasm32-unknown-unknown.
2 tests have been disabled for wasm at the moment: test
messages::search_messages and test messages::send_message_attachment.
These two tests currently rely on `std::fs` to grab a file to
send/search for using chorus. This is not possible on wasm32-unknown,
because this target does not have a Filesystem, and does not emulate on
either. These two tests should be patched, but this should be good
enough for now.
* Give tungstenite types distinct names
* reorganize files
* Better feature locking, add wasm.rs
* Implement wasm Backend
* add wasm-bindgen-test
* Build & Test for wasm
* Add macos safari wasm test
* Add wasm32 target
* Add wasm.rs test
* Move wasm-pack installation before test execution
* Fix build on wasm32
* Fix examples depending on tokio::time
* fix clippy warn
* Add example wasm bindgen test
* Add wasm-bindgen to Cargo.toml
* Add wasm test configuration
* Install wasm-bindgen-cli on linux
* Add wasm-bindgen-cli to macos
* Correct "vers" to "version"
* Attempt to locate correct geckodriver
* Run wasm tests first
* maybe this will fix ci :clueless:
* Move wasm-bindgen-cli install
* Add cargo-binstall installation script for
wasm-bindgen-cli
* Try using only one browser
* remove geckodriver
* Move all wasm related tests to macos
* Rename macOS test step for clarity
* Try out combined coverage report
* try different strategy to skip coverage on forks
* Revert "try different strategy to skip coverage on forks"
This reverts commit cae64ae5a4.
* Revert "Try out combined coverage report"
This reverts commit 584fd21076.
Flori
bitfl0wer