build(deps): bump serde_with from 1.14.0 to 2.0.0

[dependabot]

Bumps serde_with from 1.14.0 to 2.0.0.

Release notes

Sourced from serde_with's releases.

serde_with_macros v2.0.0

No changes compared to v2.0.0-rc.0.

Changed

• Make #[serde_as] behave more intuitive on Option<T> fields.

  The #[serde_as] macro now detects if a #[serde_as(as = "Option<S>")] is used on a field of type Option<T> and applies #[serde(default)] to the field. This restores the ability to deserialize with missing fields and fixes a common annoyance (#183, #185, #311, #417). This is a breaking change, since now deserialization will pass where it did not before and this might be undesired.

  The Option field and transformation are detected by directly matching on the type name. These variants are detected as Option.

  • Option
  • std::option::Option, with or without leading ::
  • core::option::Option, with or without leading ::

  If an existing default attribute is detected, the attribute is not applied again. This behavior can be supressed by using #[serde_as(no_default)] or #[serde_as(as = "Option<S>", no_default)].

Fixed

• Make the documentation clearer by stating that the #[serde_as] and #[skip_serializing_none] attributes must always be placed before #[derive].

serde_with v2.0.0

Added

• Make JsonString<T> smarter by allowing nesting serde_as definitions. This allows applying custom serialization logic, before the value gets converted into a JSON string.

  // Rust
  #[serde_as(as = "JsonString<Vec<(JsonString, _)>>")]
  value: BTreeMap<[u8; 2], u32>,
  // JSON
  {"value":"[[&quot;[1,2]&quot;,3],[&quot;[4,5]&quot;,6]]"}

Changed

• Make #[serde_as] behave more intuitive on Option<T> fields.

  The #[serde_as] macro now detects if a #[serde_as(as = "Option<S>")] is used on a field of type Option<T> and applies #[serde(default)] to the field. This restores the ability to deserialize with missing fields and fixes a common annoyance (#183, #185, #311, #417). This is a breaking change, since now deserialization will pass where it did not before and this might be undesired.

  The Option field and transformation are detected by directly matching on the type name. These variants are detected as Option.

  • Option

... (truncated)

Commits

• 625e59a Merge #491
• 427b025 Bump versions to release v2.0.0
• 8ad35a0 Merge #490
• b1190c0 Cleanup links and attributes
• 12cd92a Merge #489
• 0534f80 Suppress issue with clippy::explicit_auto_deref
• 49ebe72 Merge #487
• 69ed4a1 Make the JsonString smarter
• 6969abf Merge #484
• 9c2923e Bump versions to v2.0.0-rc.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

Merging #4785 (9e647c6) into main (e9c9ea9) will increase coverage by 0.04%.
The diff coverage is n/a.

❗ Current head 9e647c6 differs from pull request most recent head 60d7c36. Consider uploading reports for the commit 60d7c36 to get more accurate results

@@            Coverage Diff             @@
##             main    #4785      +/-   ##
==========================================
+ Coverage   78.77%   78.81%   +0.04%     
==========================================
  Files         305      305              
  Lines       38742    38169     -573     
==========================================
- Hits        30518    30084     -434     
+ Misses       8224     8085     -139     

[conradoplg]

This has a lot of changes but it looks fine, and does not seem to break existing code.

But can anyone double-check if this is safe?

@ZcashFoundation/unsafe-rust-reviewers

[teor2345]

This has a lot of changes but it looks fine, and does not seem to break existing code.

But can anyone double-check if this is safe?

@ZcashFoundation/unsafe-rust-reviewers

It pretty much follows the recommended pattern in https://doc.rust-lang.org/nightly/std/mem/union.MaybeUninit.html#initializing-an-array-element-by-element
(but with extra drop and error handling).

I checked that it drops the correct number of items.

(If anyone else wants to check, search the diff for "unsafe", the link didn't take me there automatically.)

[teor2345]

@dependabot recreate

[teor2345]

Re-approving