Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate struct builder sufficiency #111

Merged
merged 3 commits into from
Nov 17, 2020

Conversation

willscott
Copy link
Member

Check that all struct fields that are required have been set when Build'ing the Node.

@warpfork
Copy link
Collaborator

Sweet!

@warpfork warpfork merged commit d35996f into ipld:master Nov 17, 2020
warpfork added a commit that referenced this pull request Dec 4, 2020
…ll non-optional fields are present.

This continues what #111 did
and adds the same logic to the map representation.  The actual state
tracking works the same way (and was mostly already there).

Rearranged the tests slightly.

Made error messages include both field name and serial key when they
differ due to a rename directive.  (It's possible this error would get
nicer if it used a list of StructField instead of just strings, but it
would also get more complicated.  Maybe revisit later.)
warpfork added a commit that referenced this pull request Dec 4, 2020
…ll non-optional fields are present.

This continues what #111 did
and adds the same logic to the map representation.  The actual state
tracking works the same way (and was mostly already there).

Rearranged the tests slightly.

Made error messages include both field name and serial key when they
differ due to a rename directive.  (It's possible this error would get
nicer if it used a list of StructField instead of just strings, but it
would also get more complicated.  Maybe revisit later.)
@aschmahmann aschmahmann mentioned this pull request May 14, 2021
71 tasks
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