Skip to content
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

Add "Script name casing" to Project settings editor/naming #9279

Closed
ghmart opened this issue Mar 11, 2024 · 1 comment
Closed

Add "Script name casing" to Project settings editor/naming #9279

ghmart opened this issue Mar 11, 2024 · 1 comment
Labels

Comments

@ghmart
Copy link

ghmart commented Mar 11, 2024

Describe the project you are working on

All projects using GDScript.

Describe the problem or limitation you are having in your project

When attaching new GDScript it will be automatically named after node name, which is usually capitalized.

Lower-cased filenames are recommended by official documentation's "Best practices" and different Godot tutorials to avoid problems on case-insensitive filesystems.

So the user is forced to manually make script's filename lower-cased. This is annoying.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Add "Script name casing" to Project settings editor/naming (defaulting to "snake_case"). That way it will be harder to accidentally create "Name.gd" when there is already "name.gd".

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

See above.

If this enhancement will not be used often, can it be worked around with a few lines of script?

Maybe some complicated EditorScript-extending script that will traverse and report unwanted filenames. I don't know.

Is there a reason why this should be core and not an add-on in the asset library?

This is a new project setting.

@KoBeWi
Copy link
Member

KoBeWi commented Mar 11, 2024

Duplicate of #1211
This was already implemented in Godot 4.3 and will be available in the next preview release.

@KoBeWi KoBeWi closed this as not planned Won't fix, can't repro, duplicate, stale Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants