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

MapAccessor#canWrite incorrectly returns true for non-Map target #33265

Closed
sbrannen opened this issue Jul 23, 2024 · 0 comments
Closed

MapAccessor#canWrite incorrectly returns true for non-Map target #33265

sbrannen opened this issue Jul 23, 2024 · 0 comments
Assignees
@sbrannen
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone
6.2.0-M7

Comments

@sbrannen
Copy link
Member

As a follow up to #33222, I noticed that MapAccessor#canWrite should only return true for a target that is an instance of java.util.Map.
@sbrannen sbrannen added in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement labels Jul 23, 2024
@sbrannen sbrannen added this to the 6.2.0-M7 milestone Jul 23, 2024
@sbrannen sbrannen self-assigned this Jul 23, 2024
@sbrannen sbrannen added type: bug A general bug and removed type: enhancement A general enhancement labels Jul 24, 2024
@sbrannen sbrannen changed the title Ensure MapAccessor#canWrite only returns true for a Map target MapAccessor#canWrite incorrectly returns true for non-Map target Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbrannen sbrannen

Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Projects
None yet
Milestone
6.2.0-M7
Development

No branches or pull requests
1 participant
@sbrannen