Invalid code when names have spaces
See original GitHub issueWhen game object in hierarchy have names like “Some Button” generated code template has
Button Some Button {get; set;}
which causes compliation errors. Simple that comes to mind is to a trim and replace whitespaces with “_” in the names before generating identifiers. Could provide a PR over the weenekend
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to make a string that only includes spaces be ...
Please choose a valid answer.") else: print(f"Ah, I see, so your name is {my_name}?") would love to have multiple solutions to this, and...
Read more >ERROR: Invalid 'name' syntax for columns with space
Hi, I want to INSERT data into my Postgres database and it works all fine until I use column names that include spaces...
Read more >How to write SQL queries with spaces in column names
Incorrect syntax near the keyword 'Table'. SQL Server Table name with space. To fix this error, we can specify the table name in...
Read more >Incorrect error when trying to create a user with blank ...
Bug description When creating a user with space in the name (which is not allowed) an incorrect error message is shown.
Read more >How to change all invalid characters to spaces
Unfortunately, the data has invalid characters in it. ... Actually, it's probably Unicode, in UTF-8 encoding, where the code points U+0080 to U+07FF...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, you’re right. When variable names are created, they now replace all but the _ symbol with a space. Try updating Packages/packages-lock.json by changing the relevant part to
b4fd64ec4c9e018e68c80a256916ef974c84f6b3
OK, this change will go into v1.1.0. (If you are using PackageManager, you can use origin/master and it has already been applied.)