Verticality vs Horizontality v2

[EttyKitty]

I'm not exactly sure if this is the same thing, so I decided to not necro the other issue and instead write my question here. Sorry if that's wrong.

So, to start - your formatter is a godsend. After switching from a JS one, it's a breath of fresh air. Thank you.

But, I (not sure if I should say "my team", but I think we mostly agree on this) have a slight issue:
Your formatter allows choosing the max print width. I don't use it (set it to 9999), because it can cause condition checks (if (something || something2) {) or other similar things to get split into multiple lines, which I don't prefer ever (probably not the place to expand on why).
I try to keep almost all code horizontal, without arbitrary line splits.

What I'm okay with, are vertical arrays and structs. Totally fine, moreover I actually prefer these to be vertical, as, imo, they are much more readable.
But setting width to 9999 causes these to turn into unreadable one line monsters, especially structs. I'm not even sure if that's an expected behavior.

In the end I'm faced with a choice:

• Set width to 99999 and face extremely unreadable structs and/or arrays.
• Set width to something sane and get some condition checks split.

None of these is acceptable for me, and I end up having to manually tweak the code after each gobo pass, by reverting array/struct formatting and manually passing them through a JS formatter.

I saw it being mentioned that this formatter follows the Prettier option philosophy and I understand that asking for an option may be pointless, so I'm not sure what I want from you. A word of advice on what to do?

[Pizzaandy]

As mentioned in this issue, you can always create a fork and make modifications to suit your needs. For a stopgap solution, use //fmt-ignore to exclude statements from formatting.

But I think it's a fair point that RHS expressions being split up hurts the IDE experience in GameMaker on earlier versions. I'm open to implementing this, but I would want to clearly mark the option as "legacy" or similar to indicate that it's not recommended.

I've been in a holding pattern with this project because the future of GML is uncertain at the moment with new languages and GML v3 on the way. If I continue work on this project, I would be open to adding more options in the name of reaching more users - but it would make the project significantly harder to maintain.

[EttyKitty]

But I think it's a fair point that RHS expressions being split up hurts the IDE experience in GameMaker on earlier versions.

I actually work in VSCode with Stitch (with enabled line wrap, if of any importance), yet still find the splitting of RHS to be undesired from my POV.

I'm open to implementing this, but I would want to clearly mark the option as "legacy" or similar to indicate that it's not recommended.

Considering that JS formatters (example that I use) format structs vertically at all times (even if I disable the line-wrap completely), wouldn't it be easier (both in the moment and with the latter maintaining) to apply the same default rule for this formatter in regard to structs, even when width is set to 9999?
I understand that vertical arrays are a taste thing, but vertical structs seem to be a standard (I actually don't know if it is), and are the main offender for my eyes when formatted horizontally.

If the above is implemented, the only taste thing left that may benefit from a separate option would be vertical arrays (especially multidimensional and big), which is okay. I'll survive that.

I've been in a holding pattern with this project because the future of GML is uncertain at the moment with new languages and GML v3 on the way.

Understandable. My stuff is a taste wishlist, so I may in fact try to fork your project and see if I can manage to do anything (probably not).

[EttyKitty]

As a small update to this.

I decided to try my hand at modifying the source, and after a bunch of tries I was able (I think?) to implement two new options on my side (online version): Vertical Structs and Vertical Arrays, along with some other minor changes I decided to make along the way.
I'm quite happy with how it turned out, but do expect that I may've messed something up and some bugs will pop up.
Not sure if this means that the issue can be closed or not.