Some inconsistencies in default style

[RblSb]

Formatted output:

typedef Type = {f:Int}
typedef Type = {f:{f:Int}}

class Main {
	function foo():Void {
		final test:Void->Void = () -> trace(1);
		final test:() -> Void = () -> trace(1);
		final obj:{f: Int} = {f: 1};
		final obj:{f: {f: Int}} = {f: {f: 1}};
		final int:Int = 1;
	}
}

I think () -> Void and {f: Int} can be without spaces by default, so it would be easier to distinguish type vs value stuff?

[Gama11]

{f: Int} is a bug, possibly caused by using final instead of var. Spaces around -> for arrow functions and Haxe 4 style function types are working as intended.

[AlexHaxe]

sample added to https://haxecheckstyle.github.io/haxe-formatter-docs/#codesamples.WhitespaceSamples.colon_whitespace

[RblSb]

Thanks. Is there is a setting to support var:()->Void = () -> 1; style option? (separated whitespace policy for arrow function type hint)

[AlexHaxe]

{
  "whitespace": {
    "arrowFunctionsPolicy": "around",
    "functionTypeHaxe3Policy": "none",
    "functionTypeHaxe4Policy": "none"
  }
}

you can play around with these options here https://haxecheckstyle.github.io/haxe-formatter-docs/#codesamples.WhitespaceSamples.function_types_and_arrows

You can edit code area and hxformat.json on these pages, so you can safely test different code styles with your own code snippets and or formatter configuration.

[RblSb]

Thanks again, sorry for carelessness in testing!

[AlexHaxe]

no problem, the documentation pages are quite new and far from complete.
Also it's not always clear what is intentional and what is a bug, or which setting corresponds to what behaviour.