fix: correct inverted preserve_order docstring in resolve_matching_names

[alltheseas]

Summary

Fix the inverted preserve_order parameter description in the resolve_matching_names docstring.

The docstring incorrectly stated that preserve_order=True returns results in list_of_strings order, and preserve_order=False returns in query-key order. The actual behavior is the opposite:

• preserve_order=False (default): results follow list_of_strings order
• preserve_order=True: results are reordered to follow query regex key order

This is the same bug that PR #4427 fixes for the sibling function resolve_matching_names_values. This PR addresses the remaining function noted in #4493.

Fixes #4493

Changes

• Swapped the True/False descriptions in the resolve_matching_names docstring
• Added (default) annotation to the False case for clarity
• Added brief inline clarifications to the examples (matching PR Fix misleading docstring for resolve_matching_names_values #4427 style)

Signed-off-by: alltheseas alltheseas@users.noreply.github.com

[greptile-apps]

Greptile Summary

This PR corrects the inverted preserve_order parameter documentation in the resolve_matching_names function. The docstring previously had the True/False descriptions swapped - it incorrectly stated that preserve_order=True returns results in list_of_strings order and preserve_order=False returns in query-key order, when the actual behavior is the opposite.

Key changes:

• Swapped the True/False descriptions to match actual implementation behavior
• Added (default) annotation to clarify that False is the default value
• Added inline clarifications to the code examples for better understanding

The fix is verified by examining the implementation logic on lines 242-259, which shows that when preserve_order=True, the function reorders results to follow the query regex key order, not the list_of_strings order.

Confidence Score: 5/5

• This PR is completely safe to merge - it only corrects documentation without any code changes
• This is a pure documentation fix that corrects inverted parameter descriptions in a docstring. No functional code is changed, so there is zero risk of introducing bugs or breaking changes. The fix has been verified against the actual implementation logic.
• No files require special attention

Important Files Changed

Filename	Overview
source/isaaclab/isaaclab/utils/string.py	Fixes inverted preserve_order parameter documentation in resolve_matching_names function - docstring now correctly describes the actual behavior

_{Last reviewed commit: b4c20a0}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}