index variable not usable in collection selection/projection in SpEL
#23202
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: declined
A suggestion or change that we don't feel we should currently apply
Comments
spring-projects-issues
added
the
status: waiting-for-triage
rstoyanchev
added
the
in: core
sbrannen
changed the title
index variable not usable in collection selection/projection in SpEL
|
Hi @peterschubert, Thanks for raising the issue and apologies for the belated reply.
No, you're not missing anything. The team originally considered providing support for local variables in SpEL expressions, and that's evident by the code you noticed as well as various other methods in However, the Spring Framework does not make use of the local variable support in If local variables were supported in the AST and evaluation, I believe you would have been able to access that In light of that, I am closing this issue. |
sbrannen
added
status: declined
sbrannen
added a commit
that referenced
this issue
Feb 16, 2024
Since the Spring Expression Language does not actually support local
variables in expressions, this commit deprecates all public APIs
related to local variables in ExpressionState (namely, the two
enterScope(...) variants that accept local variable data,
setLocalVariable(), and lookupLocalVariable()).
In addition, we no longer invoke `state.enterScope("index", ...)` in
the Projection and Selection AST nodes since the $index local variable
was never accessible within expressions anyway.
See gh-23202
Closes gh-32004
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affects: 5.0.4
When iterating on a collection, both Selection and Projection set a variable called
indexthat contains the index of the current element.I would expect this variable to be usable in SpEL, e.g. for filtering one list based on elements of another list (or any other criterion that takes the index into account).
However, there doesn't seem to be any way to reference it.
The only code that makes use of
VariableScopeis never called.Am I missing something or is this feature not really complete?
The text was updated successfully, but these errors were encountered: