`wasm32-unknown-emscripten` build causes compilation errors

[evroon]

Cool library, thanks!

When trying to build jsonschema-py for WASM via Emcripten, I get these errors:

error[E0599]: no method named `with_http_options` found for struct `ValidationOptions<R>` in the current scope
   --> crates/jsonschema-py/src/lib.rs:977:27
    |
977 |         options = options.with_http_options(&http_opts).map_err(|e| {
    |                           ^^^^^^^^^^^^^^^^^
    |
help: there is a method `with_pattern_options` with a similar name
    |
977 -         options = options.with_http_options(&http_opts).map_err(|e| {
977 +         options = options.with_pattern_options(&http_opts).map_err(|e| {
    |

For more information about this error, try `rustc --explain E0599`.
error: could not compile `jsonschema-py` (lib) due to 1 previous error

using these commands:

rustup target add wasm32-unknown-emscripten
cargo build --target wasm32-unknown-emscripten

Is it expected that make_options calls with_http_options, where make_options can be called from WASM but with_http_options can't?

jsonschema/crates/jsonschema-py/src/lib.rs

Lines 977 to 979 in 8da0f79

	options = options.with_http_options(&http_opts).map_err(|e| {
	exceptions::PyRuntimeError::new_err(format!("Failed to configure HTTP options: {e}"))
	})?;

For context, I am trying to open a PR to add jsonschema-rs to pyodide: pyodide/pyodide-recipes#559

[evroon]

Would it maybe be possible to include an Emscripten build like @ryanking13 mentions here according to PEP 783? I can try making a PR for that if you have no objections @Stranger6667. I think it would be quite cool because then people can try out jsonschema-rs in the browser and you can provide a playground like e.g. isort provides :)

[Stranger6667]

Thanks for opening this! :) It is an oversight - I'll fix the emscripten support soon and will add a pyodide build to CI. Feel free to open a PR (and take a look at this pyodide CI job which should work here too) if you'd like to :)

Note that jsonschema already supports wasm32-unknown-unknown, so it can already be used in the browser / or any WASM runtime (via a thin wasm-bindgen-based wrapper as an option). I plan to build a playground similar to my other library (sources), but didn't get to it just yet. With pure-rust projects it is easier to build such a playground without pyodide at all to avoid unnecessary abstraction layers.

[evroon]

Awesome, thanks!