Optimize String argument resolution in MessageTag #25809
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
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.The text was updated successfully, but these errors were encountered: