`@warning_ignore` forced on a single line

[Shatur]

Input:

	@warning_ignore("integer_division")
	var body_vertex_count := body_skinning.bone_indices.size() / INFLUENCES_PER_VERTEX

Formatted like this:

	@warning_ignore("integer_division") var body_vertex_count := body_skinning.bone_indices.size() / INFLUENCES_PER_VERTEX

But looks like in docs they usually use it as an annotation.

[NathanLovato]

Closing as this is already handled by the development version on the main branch. Annotations can be inline in GDScript. There's no clear guideline, but some are usually put on the same line as the following declaration, while others are not. Now the formatter will put/keep @onready or @export annotations on the line of a declaration and keep others like @warning_ignore on a separate line.

[Shatur]

Thanks!

[fstxz]

and keep others like @warning_ignore on a separate line

Doesn't seem to be the case when the annotation is in a function, like this one:

func test_warnings():
	@warning_ignore("unused_local_constant")
	var unused_local_constant = 1

Output:

func test_warnings():
	@warning_ignore("unused_local_constant") var unused_local_constant = 1

[NathanLovato]

I see, thanks for the catch @fstxz ! I wish I had more time to work on this. I lack the time currently to finish writing the specification and e.g. grab all the GDScript codebases I can out there to massively test this and review the formatter's output across hundreds of thousands to millions of lines of GDScript code.

But well, that's kind of the limit of this kind of toolchain tool being made as a community side project (also if you're going to start doing this kind of more massive work, you'd want to expand the toolchain work and not just do this as a standalone project).

[Shatur]

I just want to say: I really appreciate your work on the formatter. It improves the experience with GDScript a lot.