spicypete

Great, refreshing read and a welcome break from the AI slopalypse.

(from a companies perspective, this is true). As a developer, you may not be paid by the task -- If I finish something early, I start work on the next thing.

In the spirit of constructive feedback, I filed an issue for you: https://github.com/reteps/dockerfmt/issues/18

I fixed this in the 0.2.8 release https://github.com/reteps/dockerfmt/releases/tag/0.2.8.

Relevant reading about the `&&` normalization. https://pkg.go.dev/encoding/json#Marshal

Then they can use one of the 14 in the `tests` directory :) https://github.com/reteps/dockerfmt/tree/main/tests

What I can do for you is fix the bugs promptly! I resolved the bugs in the `0.2.7` release. I haven't graduated college yet and don't have a full time job, so my QA skills are still improving.

This is a valid point -- I replied to why this is the way it is her: https://news.ycombinator.com/item?id=43629049. I understand it's not ideal for many, and I am open to PRs!

I am certainly not in the business of writing my own shell parser ;) Though this is a fair point -- I think I could get a more rich level of control over the output by hooking into their parser, albeit with a higher level of complexity.

I use `mvdan/sh` [1] under the hood for processing the commands. So it will reformat

  if [ foo ] ; then
    bar
  fi

to

  if [ foo ]
  then
    bar
  fi

And also format your example to

  foo
  bar

In this type of situation, it becomes a little trickier to disambiguate when I need to add semicolons and a backslash, and when I need to add only backslashes. If you use `&&` -- you have disambiguated the two cases so I can format it.

[1] https://github.com/mvdan/sh

Is there any reason you prefer `set -e` over `&&`? I'm curious if this is a readability thing.

Hi there — I’ll try to distribute a docker release of the binary tomorrow!

I got GDB working on M1 with Rosetta - it's super fast and I wanted to show off how you can do it!