[release/9.4] Simplify Aspire CLI project name validation to only reject path separators #10832
+184
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #10714 to release/9.4
/cc @mitchdenny @copilot
Customer Impact
Validation logic for
aspire new
project name was too restrictive. This change loosens it so that it only blocks using path separators and relies ondotnet new
to fail out when its rules aren't met. We block path separators because there are some specific corner cases there wheredotnet new
will acceptnot\a\valid\name
on Linux - but the app host will fail to run.Testing
Manual testing. Added test coverage
Risk
Low.
Regression?