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

Refactor: Replace hardcoded '.' with EXTENSION_SEPARATOR in StringUtils #33645

Closed
wants to merge 1 commit into from

Conversation

SungbinYang
Copy link
Contributor

This pull request refactors the StringUtils class by substituting all occurrences of the hardcoded '.' character with the already-defined constant EXTENSION_SEPARATOR. This refactor promotes cleaner code by removing magic values and enhancing maintainability, as separator characters are now managed centrally. Additionally, this change minimizes the risk of errors that may arise from inconsistent use of the '.' character throughout the codebase.

No changes have been made to the functionality of the methods, ensuring that the behavior remains intact.

Replaced all instances of the hardcoded '.' character with the EXTENSION_SEPARATOR constant in the StringUtils class.
This refactor improves the code's readability and maintainability by ensuring that separator characters are defined consistently through the use of constants.
No functional changes have been made.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 4, 2024
@bclozel
Copy link
Member

bclozel commented Oct 4, 2024

Thanks but in both cases the "." characters are not extension separators but have other meaning.

@bclozel bclozel closed this Oct 4, 2024
@bclozel bclozel added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Oct 4, 2024
@SungbinYang
Copy link
Contributor Author

Thank you for your comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants