Would love for this to get merged in. We use Pint in our pipeline and makes ide-helper a bit of a pain

Fine. I'll make changes

@mfn Made changes.

Please check the README file as I used google translate.

Not everyone has automated code styling processes set up. In such situations, the user may simply forget to run the linter and push all changes to git.
Also, the user can follow the recommendations for code style without using linters, but then he will have to manually make changes to the models each time.

Not everyone has automated code styling processes set up

I can't argue with that, I don't have numbers to prove it.

But I'm taking a step back and thinking: why add flexibility of code formatting to a library whose goal is not to format the code?

The dedicated tools are there for a reason and are much better equipped to handle this.

My argument is: if someone comes up with the idea he's not satisfied with how this library generates the code "by default",then it is time to think about adding automatic code formatting to your project. It seems backward adjusting libraries when we've the right tools already.

I'm sorry for the forth and back here and time you invested, but from my side, now that I properly understand the intention here, it's 👎🏼 to merge this PR with its current goal.