Skip to content

Add ConstructorDetector configurability to SerializationConfig too #4530

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.

Sign up for GitHub

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

Jump to bottom
Closed
cowtowncoder opened this issue May 14, 2024 · 0 comments
Closed

Add ConstructorDetector configurability to SerializationConfig too #4530

cowtowncoder opened this issue May 14, 2024 · 0 comments
Assignees
@cowtowncoder
Labels
2.18 Issues planned at 2.18 or later

Comments

@cowtowncoder
Copy link
Member

cowtowncoder commented May 14, 2024 •
edited
Loading

Describe your Issue

ConstructorDetector was added as configuration only on deserialization side (DeserializationConfig).
While this seemed sensible earlier it will actually be necessary to access from general-purpose property introspection (see #4515). So let's:

  1. Add it in SerializationConfig for 2.18
  2. (ideally) Re-factor in 3.0 to belong to lower level (MapperConfig)
@cowtowncoder cowtowncoder added to-evaluate Issue that has been received but not yet evaluated 2.18 Issues planned at 2.18 or later and removed to-evaluate Issue that has been received but not yet evaluated labels May 14, 2024
@cowtowncoder cowtowncoder self-assigned this May 14, 2024
cowtowncoder added a commit that referenced this issue May 14, 2024
@cowtowncoder
Fix #4530: make ConstructorDetector accessible on serialiation side too
15e0052
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cowtowncoder cowtowncoder

Labels
2.18 Issues planned at 2.18 or later
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cowtowncoder