Jonas Bushart

This looks reasonable overall. The types were only intended to be used as helpers for implementing `SerializeAs`/`DeserializeAs`, but a small wrapper doesn't hurt. It does look similar to `DeserializeAsWrap` now....

The option doesn't exist in v1.4.0. You need to use at least v1.4.3.

In the current state the action mainly targets the official GitHub runners. I am happy to accept PRs to expand the support here, but I have no way to test...

@dceddia Hey, if you are still interested in Windows support, could you test if the just released version v1.12 works for you?

Thanks for reporting back :) Then I hope everything works and close this issue again, until reported otherwise.

This crate is just about the serde internal data format and does not control how the format exposes it. Many human-readable formats only have the option of using a list...

> Could you name some? Sure, quick search for the keywords serde, base64, hex reveals at least these crates `base64-serde`, `hex-buffer-serde`, `hex-serde`, `serde_with`, `serde-bytes-repr`, `serde-hex`, `serdect`, `stremio-serde-hex`. If you need...

That sounds reasonable. Instead of a separate value, I think this could piggyback of the `cache-workspaces` input. That input allows specifying multiple workspaces, which might not work too well with...

Support for this is added in v1.15 with the new `rust-src-dir` input.

I think this is caused by https://github.com/serde-rs/serde/issues/2230. If you use `u64` instead of `u128` it works. You see that the `Int(u128),` variant of the enum is not being deserialized. ```...