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

Add handling when using invalid ArbitraryIntrospector #877

Merged
merged 4 commits into from
Jan 16, 2024

Conversation

seongahjo
Copy link
Contributor

@seongahjo seongahjo commented Jan 15, 2024

Summary

Add logging when using invalid ArbitraryIntrospector

(Optional): Description

  • logs when container type.
  • throws an exception if the concrete type.

How Has This Been Tested?

  • existing tests

Is the Document updated?

No

@seongahjo seongahjo added this to the 1.0.10 milestone Jan 15, 2024
@seongahjo seongahjo changed the title Add logging when using invalid ArbitraryIntrospector Add addressing when using invalid ArbitraryIntrospector Jan 15, 2024
@seongahjo seongahjo changed the title Add addressing when using invalid ArbitraryIntrospector Add handling when using invalid ArbitraryIntrospector Jan 15, 2024
sectionStart
### v1.0.10

Add handling when using invalid ArbitraryIntrospector. Logs when container type, throws an exception if the concrete type.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A detailed release-note might be better for the users!

Add exception handling when using an ArbitraryIntrospector that does not match the property type. Add a log entry if the property is of a container type, and throw an exception if the property is of a concrete type.

@seongahjo seongahjo force-pushed the sa/strict-checking branch 6 times, most recently from aa3f835 to 7b0975e Compare January 16, 2024 06:53
@seongahjo seongahjo merged commit e684cc7 into main Jan 16, 2024
11 checks passed
@seongahjo seongahjo deleted the sa/strict-checking branch January 16, 2024 07:43
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.

3 participants