Skip to content

Comments

feat!: remove strict length check on tuple deserialization#24

Merged
Stebalien merged 3 commits intoipld:mainfrom
rvagg:rvagg/nonstrict-tuple-length
Feb 13, 2025
Merged

feat!: remove strict length check on tuple deserialization#24
Stebalien merged 3 commits intoipld:mainfrom
rvagg:rvagg/nonstrict-tuple-length

Conversation

@rvagg
Copy link
Member

@rvagg rvagg commented Jan 30, 2025

This should be handled by #[serde(deny_unknown_fields)] so it can also be used non-strict (for custom visitors/deserializers). Unfortunately this isn't supported upstream in serde yet, so we should work on that.

This should be handled by #[serde(deny_unknown_fields)] so it can also be used
non-strict (for custom visitors/deserializers). Unfortunately this isn't
supported upstream in serde yet, so we should work on that.
rvagg added a commit to rvagg/serde_ipld_dagcbor that referenced this pull request Jan 30, 2025
Depends on: ipld/rust-ipld-core#24

This should be handled by #[serde(deny_unknown_fields)] so it can also be used
non-strict (for custom visitors/deserializers). Unfortunately this isn't
supported upstream in serde yet, so we should work on that.
@rvagg rvagg marked this pull request as ready for review February 12, 2025 23:08
@Stebalien Stebalien force-pushed the rvagg/nonstrict-tuple-length branch from e54ea58 to 6303592 Compare February 12, 2025 23:10
rvagg added a commit to rvagg/serde_ipld_dagcbor that referenced this pull request Feb 13, 2025
Depends on: ipld/rust-ipld-core#24

This should be handled by #[serde(deny_unknown_fields)] so it can also be used
non-strict (for custom visitors/deserializers). Unfortunately this isn't
supported upstream in serde yet, so we should work on that.
@Stebalien Stebalien merged commit 6b10709 into ipld:main Feb 13, 2025
6 checks passed
@rvagg rvagg deleted the rvagg/nonstrict-tuple-length branch February 13, 2025 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants