Skip to content

Fix method naming to follow Java camelCase conventions#48640

Closed
GaoSSR wants to merge 1 commit intospring-projects:mainfrom
GaoSSR:fix-method-naming-convention
Closed

Fix method naming to follow Java camelCase conventions#48640
GaoSSR wants to merge 1 commit intospring-projects:mainfrom
GaoSSR:fix-method-naming-convention

Conversation

@GaoSSR
Copy link
Copy Markdown
Contributor

@GaoSSR GaoSSR commented Dec 30, 2025

This PR fixes a method naming issue in LocalHttpClientTransport where the method name createhttpClientConnectionOperator does not follow standard Java camelCase naming conventions.

Changes

Renamed createhttpClientConnectionOperator to createHttpClientConnectionOperator to ensure proper capitalization of the "Http" portion of the method name, following Java naming conventions where each word in a compound name should start with an uppercase letter.

Why This Matters

Consistent naming conventions improve code readability and maintainability. The original method name createhttpClientConnectionOperator incorrectly uses lowercase "http" instead of "Http", which deviates from the standard Java camelCase convention used throughout the Spring Boot codebase.

Rename createhttpClientConnectionOperator to createHttpClientConnectionOperator
to follow standard Java camelCase naming conventions where each word
in a compound name should start with an uppercase letter.

Signed-off-by: 高春晖 <18220699480@163.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 30, 2025
@snicoll snicoll self-assigned this Dec 30, 2025
@snicoll snicoll added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 30, 2025
@snicoll snicoll added this to the 3.5.10 milestone Dec 30, 2025
snicoll pushed a commit that referenced this pull request Dec 30, 2025
See gh-48640

Signed-off-by: 高春晖 <18220699480@163.com>
@snicoll snicoll closed this in a3d1e01 Dec 30, 2025
@snicoll
Copy link
Copy Markdown
Member

snicoll commented Dec 30, 2025

@GaoSSR thank you for the PR. FYI, we do not need a lengthy description that seems to be generated by a LLM for a two lines change. Such PR can be reviewed based on the merit of the code only.

@GaoSSR
Copy link
Copy Markdown
Contributor Author

GaoSSR commented Dec 30, 2025

Thanks for the feedback,I'll keep the description brief next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: task A general task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants