Skip to content

Conversation

izeye
Copy link
Contributor

@izeye izeye commented Jan 29, 2025

It seems to be a duplicate of shouldNotRegisterStructuredLoggingJsonMembersCustomizerRuntimeHintsWhenCustomizerIsNotSet() practically.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 29, 2025
@philwebb philwebb added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 29, 2025
@philwebb philwebb added this to the 3.5.0-M2 milestone Jan 29, 2025
philwebb pushed a commit that referenced this pull request Jan 29, 2025
Remove shouldNotRegisterStructuredLoggingJsonMembersCustomizer...
RuntimeHints since it duplicates shouldNotRegisterStructuredLogging...
JsonMembersCustomizerRuntimeHintsWhenCustomizerIsNotSet

See gh-44013

Signed-off-by: Johnny Lim <[email protected]>
@philwebb philwebb closed this in eeee7d9 Jan 29, 2025
@philwebb
Copy link
Member

Thanks @izeye!

@izeye izeye deleted the patch-56 branch January 29, 2025 04:23
@nosan
Copy link
Contributor

nosan commented Jan 29, 2025

Not exactly

shouldNotRegisterStructuredLoggingJsonMembersCustomizerRuntimeHints checks the following condition

return (properties != null) ? AotContribution.get(properties.allCustomizers()) : null (when the properties variable is null)

shouldNotRegisterStructuredLoggingJsonMembersCustomizerRuntimeHintsWhenCustomizerIsNotSet
checks when the properties variable is not null but customizers are empty.

@philwebb
Copy link
Member

Whoops, I guess I should revert this then?

@nosan
Copy link
Contributor

nosan commented Jan 29, 2025

I think yes :)

@izeye
Copy link
Contributor Author

izeye commented Jan 29, 2025

Sorry, I thought it's a duplicate based on their names.

I created #44014 to restore it with rename to reflect its intention.

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.

4 participants