Skip to content

NamespaceParser now recognizes API version identifiers starting with '_'#1172

Merged
commonsensesoftware merged 2 commits intomainfrom
dev/xavier/_namespace
Mar 9, 2026
Merged

NamespaceParser now recognizes API version identifiers starting with '_'#1172
commonsensesoftware merged 2 commits intomainfrom
dev/xavier/_namespace

Conversation

@xavierjohn
Copy link
Collaborator

@xavierjohn xavierjohn commented Mar 9, 2026

Support underscore-prefixed API version identifiers

  • You've read the Contributor Guide and Code of Conduct.
  • You've included unit or integration tests for your change, where applicable.
  • You've included inline docs for your change, where applicable.
  • There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Summary of the changes (Less than 80 chars)

Description

NamespaceParser now recognizes API version identifiers starting with '_', in addition to 'v' and 'V'. Added comprehensive tests to ensure correct parsing of underscore-prefixed version formats in various namespace scenarios.

NamespaceParser now recognizes API version identifiers starting with '_', in addition to 'v' and 'V'. Added comprehensive tests to ensure correct parsing of underscore-prefixed version formats in various namespace scenarios.
Updated XML comments and code documentation in NamespaceParser.cs to specify that API version parsing supports 'v', 'V', or '_' as valid namespace prefixes. Added remarks and examples explaining the use of the underscore prefix, especially for folder names starting with numbers. Improved TryParse parameter documentation to reflect these changes.
@commonsensesoftware commonsensesoftware merged commit da42c25 into main Mar 9, 2026
6 checks passed
@commonsensesoftware commonsensesoftware deleted the dev/xavier/_namespace branch March 9, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants