leftCurly: both with anonymous types

[gene-pavlovsky]

Describe the bug

With lineEnds.leftCurly option set to both, the anonymous object type declarations have an unwanted newline added before (but not after) the {.

Input file

typedef Point2D = {x:Int, y:Int};
typedef Point3D = {x:Int, y:Int, z:Int};

class A {
	var a:{x:Int, y:Int, z:Int};
}

Broken output

typedef Point2D =
{x:Int, y:Int};

typedef Point3D =
{x:Int, y:Int, z:Int};

class A
{
	var a:
		{x:Int, y:Int, z:Int};
}

[gene-pavlovsky]

With formatter 1.5.1, the output looks like this now:

typedef Point2D =
{
	x:Int,
	y:Int
};

typedef Point3D =
{
	x:Int,
	y:Int,
	z:Int
};

class A
{
	var a:
		{x:Int, y:Int, z:Int};
}

[AlexHaxe]

I've created a testcase for #301 (https://github.com/HaxeCheckstyle/haxe-formatter/blob/master/test/testcases/lineends/issue_301_typedef_anon_type.hxtest), so technically it should work - since TravisCI is green.
I guess your configuration has additional options that come into play here.

Can you narrow your configuration down to help figure out why it fails for you?

[gene-pavlovsky]

{
	"lineEnds": {
		"leftCurly": "both"
	},
	"wrapping": {
		"anonType": {"defaultWrap": "keep"}
	}
}

results in

	var a:
		{x:Int, y:Int, z:Int};

P.S. At my workplace we have a weird style where left curly is usually on a new line, but in case of literal objects or anonymous types it's on the same line. There's no setting to achieve that, right?

[AlexHaxe]

thanks, that indeed misbehaves...

no, there is currently no setting allowing different curly options for object literals or anon types, see #346
I think @cmandlbaur was working on some parts of it, but I'm not sure how far he got

[gene-pavlovsky]

Thanks for the link, I left a comment there as it didn't include my anonymous type case