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

Make SpEL's OptimalPropertyAccessor private #32410

Closed
sbrannen opened this issue Mar 10, 2024 · 0 comments
Closed

Make SpEL's OptimalPropertyAccessor private #32410

sbrannen opened this issue Mar 10, 2024 · 0 comments
Assignees
@sbrannen
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone
6.2.0-M1

Comments

@sbrannen
Copy link
Member

sbrannen commented Mar 10, 2024 •
edited
Loading

It was never necessary for SpEL's OptimalPropertyAccessor to be public.

Instead, clients should interact with OptimalPropertyAccessor exclusively via the CompilablePropertyAccessor API.

In light of that, we should make SpEL's OptimalPropertyAccessor private in 6.2.
@sbrannen sbrannen added in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement labels Mar 10, 2024
@sbrannen sbrannen added this to the 6.2.0-M1 milestone Mar 10, 2024
@sbrannen sbrannen self-assigned this Mar 10, 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: enhancement A general enhancement
Projects
None yet
Milestone
6.2.0-M1
Development

No branches or pull requests
1 participant
@sbrannen