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

Replace hardcoded "null" with NULL_STRING constant in ObjectUtils.nullSafeConciseToString() #33625

Conversation

nomoreFt
Copy link
Contributor

@nomoreFt nomoreFt commented Oct 1, 2024

Description:

This pull request replaces the hardcoded "null" string in the nullSafeConciseToString method with the existing NULL_STRING constant to improve maintainability and readability.

Changes:

Replaced occurrences of the hardcoded "null" string with the already declared NULL_STRING constant.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 1, 2024
@sbrannen sbrannen self-assigned this Oct 1, 2024
@sbrannen sbrannen added type: task A general task in: core Issues in core modules (aop, beans, core, context, expression) and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Oct 1, 2024
@sbrannen sbrannen changed the title Replace hardcoded "null" with NULL_STRING constant in ObjectUtils#nullSafeConciseToString Replace hardcoded "null" with NULL_STRING constant in ObjectUtils.nullSafeConciseToString() Oct 1, 2024
@sbrannen sbrannen merged commit 893f5dc into spring-projects:main Oct 1, 2024
1 check passed
@sbrannen
Copy link
Member

sbrannen commented Oct 1, 2024

Good catch!

That was an oversight on my part.

This has been merged into main.

Thanks

@sbrannen sbrannen added this to the 6.2.0-RC2 milestone Oct 19, 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: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants