-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Improve diagnostics in SpEL for repeated text #30142
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
Comments
sbrannen
added
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
labels
Mar 19, 2023
github-actions
bot
added
status: backported
An issue that has been backported to maintenance branches
and removed
for: backport-to-5.3.x
labels
Mar 19, 2023
izeye
added a commit
to izeye/spring-framework
that referenced
this issue
Mar 23, 2023
jgallimore
pushed a commit
to tomitribe/spring-framework
that referenced
this issue
Mar 31, 2023
Attempting to create repeated text in a SpEL expression using the repeat operator can result in errors that are not very helpful to the user. This commit improves the diagnostics in SpEL for the repeat operator by throwing a SpelEvaluationException with a meaningful error message in order to better assist the user. Closes spring-projectsgh-30142
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: enhancement
A general enhancement
Attempting to create repeated text in a SpEL expression can result in errors that are not very helpful to the user.
We should therefore improve the diagnostics so that the user is provided a meaningful error message.
The text was updated successfully, but these errors were encountered: