Skip to content

Validate project name and fix pathing for project templates. #9157

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

Merged
merged 1 commit into from
May 9, 2025

Conversation

mitchdenny
Copy link
Member

Fixes: #9112

The original issue showed using an invalidate template name but that was a misunderstanding of the CLI. The template name is the argument, the name is an option, although after some testing, I realized that we need to do some more validation on the template name.

For now, I've restricted it to the same as assembly naming requirements (roughly). We can loosen it up a bit if we need to.

@mitchdenny mitchdenny merged commit 80565e9 into main May 9, 2025
174 checks passed
@mitchdenny mitchdenny deleted the mitchdenny/project-name-validation branch May 9, 2025 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[AspireE2E] When using the "aspire new" command and add extra characters/words, it has been accepted.
2 participants