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

CompoundExpression omits null-safe syntax in AST string representation of null-safe selection/projection in SpEL #32515

Closed
sbrannen opened this issue Mar 22, 2024 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@sbrannen
Copy link
Member

The AST string representations of the following SpEL expressions currently omit the null-safe navigation operator (?.) that was present in the original expression.

  • null-safe projection: {1,2,3}?.![#isEven()] --> {1,2,3}.![#isEven()]
  • null-safe selection: {1,2,3}?.?[#isEven(#this)] --> {1,2,3}.?[#isEven(#this)]
  • null-safe select first: {1,2,3}?.^[#isEven(#this)] --> {1,2,3}.^[#isEven(#this)]
  • null-safe select last: {1,2,3}?.$[#isEven(#this)] --> {1,2,3}.$[#isEven(#this)]
@sbrannen sbrannen added type: bug A general bug in: core Issues in core modules (aop, beans, core, context, expression) labels Mar 22, 2024
@sbrannen sbrannen added this to the 6.1.6 milestone Mar 22, 2024
@sbrannen sbrannen self-assigned this Mar 22, 2024
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) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant