This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #37
add testing in CI for
wasm
targets. Testing in WASM is a bit weird right now, since you need a wasm environment to actually run in. Also no wasm testing solutions support doctests (and even if they did most of the doctests in color-eyre depend on doing something like reading to STDOUT/STDIN, which most WASM ABIs don't have AFAIK).As such the following has been done here:
wasm-pack
&&wasm-bindgen-test
.#[wasm_bindgen_test]
.Hopefully the approach is okay? WASM made it a bit awkward, but I figured may as well start off the PR with what works. Ideally once tracing has added in wasm test support, we can also validate the tracing bit of functionality with another
#[wasm_bindgen_test]
, I figured we shouldn't add that before incase they accidentally break it somehow without meaning to because they aren't testing it.