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

[TECH-DEBT] Move to jackson json provider in JsonPath instead of jsonsmart #648

Closed
a1shadows opened this issue Mar 18, 2024 · 4 comments
Closed
Assignees

Comments

@a1shadows
Copy link
Collaborator

a1shadows commented Mar 18, 2024

We can have uniformity across the repo if we do this and can avoid pulling in the json-smart dependency

was raised during #647

@baulea
Copy link
Contributor

baulea commented Mar 18, 2024

@a1shadows You may assign this issue to me. I'll have a closer look at json array handling :-)

@baulea
Copy link
Contributor

baulea commented Mar 23, 2024

@a1shadows Do you know the reason, why Gson is used in the Kafka part? Couldn't that also be changed to Jackson?

@a1shadows
Copy link
Collaborator Author

shadows Do you know the reason, why Gson is used in the Kafka part? Couldn't that also be changed to Jackson?

Hey @authorjapps any idea on this?

@authorjapps
Copy link
Owner

authorjapps commented Mar 24, 2024

Gson is used in the Kafka part?

@a1shadows, I vaguely remember, a collaborator introduced for a quick fix. I think it was introduced for Kafka "headers" (and elsewhere) to allow generic object structure ser/de using Gson easily over Jackson.
Yes, Jackson can be used instead of Gson 👍 .

Worth checking anywhere else Gson is not used before completely getting rid of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants