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.

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

BeanDeserializerModifier::updateProperties doesn't work #4358

Open
1 task done
herkrath opened this issue Feb 1, 2024 · 1 comment
Open
1 task done

BeanDeserializerModifier::updateProperties doesn't work #4358

herkrath opened this issue Feb 1, 2024 · 1 comment
Labels
2.17 Issues planned at earliest for 2.17 has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue

Comments

@herkrath
Copy link
Contributor

herkrath commented Feb 1, 2024 •
edited

Search before asking

  • I searched in the issues and found nothing similar.

Describe the bug

At least changing the order doesn't work via BeanDeserializerModifier::updateProperties, maybe actions like add/remove too. Returning a different order has no effect.

This issue originates from #4351.

Version Information

2.16.1

Reproduction

Explanatory unit tests are part of my PR #4359.

Expected behavior

The order defined via the result of BeanDeserializerModifier::updateProperties shall define the order of the deserialization (i.e. the invoking of the deserializers and setter methods).

Additional context

No response
@herkrath herkrath added the to-evaluate Issue that has been received but not yet evaluated label Feb 1, 2024
@herkrath herkrath mentioned this issue Feb 1, 2024
Merged
cowtowncoder pushed a commit that referenced this issue Feb 10, 2024
@herkrath
UTs for issue #4358 (#4359)
bbcbb67
@cowtowncoder cowtowncoder added has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue 2.17 Issues planned at earliest for 2.17 and removed to-evaluate Issue that has been received but not yet evaluated labels Feb 10, 2024
@cowtowncoder
Copy link
Member

Merged (failing) tests for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2.17 Issues planned at earliest for 2.17 has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cowtowncoder @herkrath