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

SpEL ConstructorReference does not generate AST representation of arrays #29665

Closed
sbrannen opened this issue Dec 8, 2022 · 0 comments
Closed
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Milestone

Comments

@sbrannen
Copy link
Member

sbrannen commented Dec 8, 2022

Given a SpEL expression such as new String[3], an invocation of toStringAST() on the parsed SpelExpression results in new String() instead of new String[3].

This is due to the fact that implementation of toStringAST() in ConstructorReference does not take arrays into consideration.

@sbrannen sbrannen added type: bug A general bug in: core Issues in core modules (aop, beans, core, context, expression) for: backport-to-5.3.x labels Dec 8, 2022
@sbrannen sbrannen added this to the 6.0.3 milestone Dec 8, 2022
@sbrannen sbrannen self-assigned this Dec 8, 2022
@github-actions github-actions bot added status: backported An issue that has been backported to maintenance branches and removed for: backport-to-5.3.x labels Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant