Style: Consolidate & migrate GDScript .editorconfig
#96965
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.editorconfig
to the projects. #96845The above PR introduced an issue where running GDScript tests will create a
.editorconfig
file inmodules/gdscript/tests/scripts/
. While it could be added as an ignored item in the local.gitignore
, the generated file definesroot = true
, so all other config options would be erroneously discarded.This fixes the issue by making use of the new intended behavior: a pre-existing
.editorconfig
. While a blank file would work, it felt much more appropriate to coincide this a minor style cleanup of the.editorconfig
files already in the GDScript module. So now, rather than going from 2→3 files, we're going from 2→1, as all the relevant attributes can be safely handled in a single file (only.gd
/.out
were given attributes, and they're exclusively found in the test project itself).