Skip to content

[release/9.4] Simplify Aspire CLI project name validation to only reject path separators #10832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: release/9.4
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 5, 2025

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 on dotnet new to fail out when its rules aren't met. We block path separators because there are some specific corner cases there where dotnet new will accept not\a\valid\name on Linux - but the app host will fail to run.

Testing

Manual testing. Added test coverage

Risk

Low.

Regression?

@mitchdenny mitchdenny self-requested a review August 5, 2025 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants