Two-lined export annotation are always placed after one-lined annotations

[blabdouze]

Given :

@export
var test_first: int

@export var test_second: int

It will be reformated as :

@export var test_second: int

@export
var test_first: int

Is this intended behaviour ?

For some cases when we have some setter/ long annotation we prefer to have this formatting :

@export_range(1, 30, 1, "prefer_slider") 
var min_tiles: int = 3:
	set = _set_min_tiles

I don't think the order of export should be modified by the formater.

[NathanLovato]

No, it's probably a case that's not supported or handled specifically at the moment.

Would you happen to have a chunk of a script from your project where you have this problem that you could share? Just the variables to have some more snippets handy to test and debug.

[blabdouze]

Of course, let me share where it happen :

## Tileset coordinates to use
@export var tileset_coords: Vector2i:
	set = _set_tileset_coords
## Only used in editor for preview of current tileset_coords
@export var tileset_preview: Image

## Minimal tiles count in generated chunk
@export_range(1, 30, 1, "prefer_slider")
var min_tiles: int = 3:
	set = _set_min_tiles

## Maximal tiles count in generated chunk
@export_range(1, 30, 1, "prefer_slider")
var max_tiles: int = 8:
	set = _set_max_tiles
	
## Jitter probability when generating a chuck. [br]
##  - 0 means all chunks will look the same [br]
##  - 0.5 makes the chunk go wild
@export_range(0, 0.5, 0.05) var jitter: float = 0.25

## Medium coverage wanted
@export_range(0, 100, 1, "prefer_slider", "suffix: %") var coverage: int = 30

This was reformated as :

## Tileset coordinates to use
@export var tileset_coords: Vector2i:
	set = _set_tileset_coords
## Only used in editor for preview of current tileset_coords
@export var tileset_preview: Image

## Jitter probability when generating a chuck. [br]
##  - 0 means all chunks will look the same [br]
##  - 0.5 makes the chunk go wild
@export_range(0, 0.5, 0.05) var jitter: float = 0.25

## Medium coverage wanted
@export_range(0, 100, 1, "prefer_slider", "suffix: %") var coverage: int = 30

## Minimal tiles count in generated chunk
@export_range(1, 30, 1, "prefer_slider")
var min_tiles: int = 3:
	set = _set_min_tiles

## Maximal tiles count in generated chunk
@export_range(1, 30, 1, "prefer_slider")
var max_tiles: int = 8:
	set = _set_max_tiles

min_tiles and max_tiles should remain above jitter and coverage.

This is the workaround I have for 0.25 :

## Tileset coordinates to use
@export var tileset_coords: Vector2i:
	set = _set_tileset_coords
## Only used in editor for preview of current tileset_coords
@export var tileset_preview: Image

## Minimal tiles count in generated chunk
@export_range(
	1,
	30,
	1,
	"prefer_slider",
) var min_tiles: int = 3:
	set = _set_min_tiles

## Maximal tiles count in generated chunk
@export_range(
	1,
	30,
	1,
	"prefer_slider",
) var max_tiles: int = 8:
	set = _set_max_tiles

## Jitter probability when generating a chuck. [br]
##  - 0 means all chunks will look the same [br]
##  - 0.5 makes the chunk go wild
@export_range(0, 0.5, 0.05) var jitter: float = 0.25

## Medium coverage wanted
@export_range(0, 100, 1, "prefer_slider", "suffix: %") var coverage: int = 30

But i doesn't look quite right to me, the @export_range args are split and it's less readable.

[NathanLovato]

Note for self, it's happening because:

• In one case (annotation and var definition on two lines) we have a sibling annotation and variable statement AST nodes.
• In the other case (all on one line), we have a variable statement with a child annotations and grandchild annotation node.

Need to normalize them from the reorder module's perspective, so they get treated as the same thing.