Skip to content

Optimize String argument resolution in MessageTag #25809

@jhoeller

Description

@jhoeller

MessageTag.resolveArguments contains old logic for checking a single String array element which seems to be dead code since a String element can never be an array itself, making all the differentiation pointless since we'll always return the given String anyway. Streamlining this towards a straight return of the original String array is not only easier to read but also avoids wasting CPU cycles.

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchestype: enhancementA general enhancement

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions