-
Notifications
You must be signed in to change notification settings - Fork 31
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
make oneOf and anyOf throw at build time rather then on deserialization #1001
Conversation
93899cd
to
1649721
Compare
packages/dynamite/dynamite_end_to_end_test/test/nested_ofs_test.dart
Outdated
Show resolved
Hide resolved
1649721
to
6817462
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you didn't correctly run dart fix in the end. Other than that and the small nitpick LGTM
packages/dynamite/dynamite_end_to_end_test/lib/nested_ofs.openapi.json
Outdated
Show resolved
Hide resolved
These weren't accidental but just the builder failing due to #1024 and I just didn't notice it. |
I think that particular one is by accident since you created a new property instead of setting the property to be required. All other ones are correct. |
6817462
to
dfc79b5
Compare
packages/dynamite/dynamite_end_to_end_test/lib/nested_ofs.openapi.dart
Outdated
Show resolved
Hide resolved
dfc79b5
to
3ab8f3e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebase, then it will pass
…her then on deserialization Signed-off-by: Nikolas Rimikis <leptopoda@users.noreply.github.com>
3ab8f3e
to
ec77029
Compare
Also correctly requires oneOf to only have one matching member.
Depends on #999 thus also blocked on the spec being corrected