-
Notifications
You must be signed in to change notification settings - Fork 519
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
Try a project with a space in Name #8468
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there already some AOT special characters tests that do this? Otherwise, seems like a good test case to add if it passes.
It doesn't test that the "ProjectName" has spaces in it. Just the path to the project has special chars I think |
27a58c3
to
190ffa9
Compare
32e62eb
to
72240ef
Compare
72240ef
to
c5c065f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise, LGTM.
[TestCase ("Test Me")] | ||
// testing characters as per https://www.compart.com/en/unicode/category/Zs | ||
[TestCase ("TestUnicodeSpace0020\u0020Me")] | ||
// TODO these break with AOT error on windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to make the tests run only on macOS and Linux?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can.
We have on occasion had reports of users using a space in their "Project Name". We already have a test which checks for spaces in the path, but not in the project name. This commit adds this test and fixes up a few area's where this caused a problem.
It should be noted that certain unicode based characters still cause issues with the .net Aot compiler. These unit test cases have been commented out for now.