Skip to content

Deprecate spring.gson.lenient in favor of a new spring.gson.strictness property #41430

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

Closed
wilkinsona opened this issue Jul 9, 2024 · 1 comment
Assignees
Labels
type: enhancement A general enhancement
Milestone

Comments

@wilkinsona
Copy link
Member

wilkinsona commented Jul 9, 2024

When doing this, we may want to duplicate the Strictness enum in our own code to preserve backwards compatibility with earlier versions of Gson. That said, I'm not sure how common it will be to want to downgrade the version of Gson so the duplication may not be necessary. Flagging for team attention to see what everyone else thinks.

@wilkinsona wilkinsona added type: enhancement A general enhancement for: team-attention An issue we'd like other members of the team to review labels Jul 9, 2024
@wilkinsona wilkinsona added this to the 3.4.x milestone Jul 9, 2024
@philwebb
Copy link
Member

We've decided to use the GSON enum. We can introduce our own if a compelling reason is raised.

@philwebb philwebb removed the for: team-attention An issue we'd like other members of the team to review label Jul 10, 2024
@wilkinsona wilkinsona self-assigned this Jul 12, 2024
@wilkinsona wilkinsona modified the milestones: 3.4.x, 3.4.0-M1 Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants