Repository navigation
[PROPOSAL] ModelTestCase.mapper improvements #770
Description
Activity
100% thanks!
@dblock Do you think that both mapper should support here? I think I can work on it once the decision is made.
Hi @channel-dante and @dblock , we are adding a
default MapperinJsonUtilsin this PR , please follow this comment to know the context, I think we can use that , rather than hardcoding one of them, the idea is to take the provider from the classpath instead of hardcoding one of the jakarta or JacksonCaution : the methods in the mapper are overridden to provide support for the classes which implement
JsonpSerializableI am not sure what the implications of either are, let's look at the code! Thank you.
Hi, I'd like to work on this issue.
I investigated ModelTestCase and confirmed it still randomly chooses between JsonbJsonpMapper and JacksonJsonpMapper using RAND.
Since the proposed JsonUtils mentioned in the discussion doesn't exist in the current main branch, I'd like to confirm the expected solution before implementing it.
Should ModelTestCase:
- Always use a single mapper (Jackson or JsonB), or
- Be updated to run deterministically with both mappers?
What/Why
What are you proposing?
What problems are you trying to solve?
What is the developer experience going to be?