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

Remove duplicate code in NettyWebServerFactoryCustomizer #37434

Closed
wants to merge 1 commit into from
Closed

Remove duplicate code in NettyWebServerFactoryCustomizer #37434

wants to merge 1 commit into from

Conversation

shin-mallang
Copy link
Contributor

Since the PropertyMapper's alwaysApplyingWhenNonNull() has already been called, the subsequent whenNonNull() is unnecessary.

Since the PropertyMapper's alwaysApplyingWhenNonNull() has already been called, the subsequent whenNonNull() is unnecessary.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 15, 2023
@philwebb philwebb added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 18, 2023
@philwebb philwebb added this to the 3.2.x milestone Sep 18, 2023
@philwebb philwebb self-assigned this Sep 18, 2023
@wilkinsona wilkinsona changed the title Remove duplicate code in NettyWebServerFactoryCustomizer. Remove duplicate code in NettyWebServerFactoryCustomizer Sep 22, 2023
@philwebb philwebb removed their assignment Sep 25, 2023
@mhalbritter mhalbritter self-assigned this Sep 28, 2023
mhalbritter pushed a commit that referenced this pull request Sep 28, 2023
Since the PropertyMapper's alwaysApplyingWhenNonNull() has already been
called, the subsequent whenNonNull() is unnecessary.

See gh-37434
@mhalbritter mhalbritter modified the milestones: 3.2.x, 3.2.0-RC1 Sep 28, 2023
@mhalbritter
Copy link
Contributor

Thank you!

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.

None yet

4 participants