Bela VanderVoort

There are some interesting side effects that make me want to explore it more. Ones that are better ```c# string disableSuppressRedirect = appSettings.Get( AppSettingsSuppressFormsAuthenticationRedirectKey ); // is now string disableSuppressRedirect...

I believe this is really a problem for #7

This is kind of an edge case of #451 Constructors aren't an InvocationExpression, but it can start a chain of them and we should break on the .GetFilessssssss first

This is how prettier deals with somewhat similar statements, they aren't super consistent between them either ```js const shorterName: someFunc = (syntaxTrivia) => CallSomething( VisualBasic.SyntaxKind.CommentTrivia, jlasdjfklaskdfakjsdfkjasdf ); const s_isVisualBasicCommentTrivia: someFunc...

Another example ```c# // random comment // other random comment public void Method() { } ``` I'm thinking maybe lines between and after comments should be removed.

This will most likely require conditional groups somewhere. At least prettier uses them. See `call-arguments.js` These are some of the related cases with possible desired formatting. ```c# entity.HasKey(e => new...

see CommandLineFormatter line 129 or so

The code in RightHandSide is probably what needs to change, but there are a ton of edge cases that get ruined every time I attemp to figure out how to...

There is also the question of if ```c# this should break, because it has multiple items private string[] SomeArray = new[] { "SomeValue_____________________", "SomeValue_____________________", }; // or if it should...

Also note that prettier doesn't do this for objects or arrays ```js var someSemiLongName_____________ = { one: "one_____________________________________", }; var someSemiLongName_____________ = [ "one_____________________________________", ];