Skip to content

Conversation

@JacksonJang
Copy link
Contributor

This issue has already been resolved through #5466,
so I moved this test out of tofix package.

@@ -33,7 +31,6 @@ void failOnUnknownPropertyUnwrapped() throws Exception {
final String JSON = "{'field': 'value', 'bad':'bad value'}";
try {
mapper.readValue(a2q(JSON), A.class);
fail("Exception was not thrown on unknown property");
Copy link
Member

Choose a reason for hiding this comment

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

What?! No. This is the whole thing to check -- why issue #650 is still valid.

@cowtowncoder
Copy link
Member

@JacksonJang I don't think #650 has been resolved: the expected exception is not being thrown.
Please re-read #650 if you want, has nothing to with Records; #5466 not directly relevant as far as I can see.

@JacksonJang
Copy link
Contributor Author

@cowtowncoder
I'm really sorry about that..
it looks like I misunderstood the issue.

thank you for pointing it out.

@cowtowncoder
Copy link
Member

Also: yes, CI was failing for all users due to CI / code-coverage change, but now fixed I hope.

@JacksonJang JacksonJang deleted the fix-650 branch December 11, 2025 09:15
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