`--reorder-code` inserts a space before subscript brackets (`foo()[i]` → `foo() [i]`) and expands empty dict `{}` to `{ }`, diverging from the official GDScript style guide

[minami110]

Tested on gdscript-formatter 0.21.0 (Pre-release 0.21.0-beta, published 2026-07-12), Linux x86_64. Upstream main checked up to 248fa13b (2026-07-12 09:20 UTC) — no fix commit found.

The empty-dict part ({} → { }) looks like a regression of #152 "Formatter is inserting a space inside of empty dictionary literals" (closed).

Impact (style-guide deviation, non-breaking)

The GDScript style guide — Whitespace section shows array[3] and dict["key"] with no space between the closing )/identifier/}/] and the following [. Formatter output diverges from that.

Trigger

Any subscript on the result of a call or cast — foo()[i], (x as Dictionary)[key], arr.split(".")[0]. Also any empty dict literal {}.

Repro

Input (bug.gd):

func demo() -> void:
	var d: Dictionary = {}
	var v: Variant = (d as Dictionary)["key"]
	print(v)

Command:

gdscript-formatter --stdout --reorder-code bug.gd

Actual output

func demo() -> void:
	var d: Dictionary = { }
	var v: Variant = (d as Dictionary) ["key"]
	print(v)

Expected (per official style guide)

func demo() -> void:
	var d: Dictionary = {}
	var v: Variant = (d as Dictionary)["key"]
	print(v)

[NathanLovato]

Thanks for the reports. Just so you know a space in empty dictionaries is actually the official style guideline. The goal being to make dictionary definitions easier to visually distinguish from arrays: { } vs [] / { my_key: "value" } vs [my_key, "value"]

Although, the official style guide does not very precisely specify those details.

The space after the type cast and before the subscript should definitely not be there.

I won't comment on every issue you open but I just want to say I appreciate you taking the time to test and report these very much.

[minami110]

Thanks for the reports. Just so you know a space in empty dictionaries is actually the official style guideline. The goal being to make dictionary definitions easier to visually distinguish from arrays: { } vs [] / { my_key: "value" } vs [my_key, "value"]

Although, the official style guide does not very precisely specify those details.

The space after the type cast and before the subscript should definitely not be there.

I won't comment on every issue you open but I just want to say I appreciate you taking the time to test and report these very much.

I wasn't aware of the { } convention — thank you for the clarification! I also hope opening so many issues at once wasn't too much of a bother. The reports came from running reformat on a personal project in a Japanese-language environment and collecting the issues that surfaced. Multibyte identifiers are probably not considered best practice, so please feel free to prioritize (or deprioritize) as you see fit. Either way, I'm rooting for this project!

[NathanLovato]

Having as many issues as there are with the formatter open at once is no bother at all, it's the contrary: I want to keep improving it for everyone. And I think it's perfectly fine to write the code in your native language.