Skipping a post for haxe-formatter 1.2.0, because I released formatter 1.3.0 earlier (for those using VSCode, there is vshaxe 2.4.5 out now as well).
There are some breaking changes in that new version, if you were using custom values for
you need to update your configuration and use the new
There is a full dump of all built-in default options under
resources/default-hxformat.json inside your haxelib folder (you can also generate your own version by running
haxelib run formatter --default-config <filename>).
Again VSCode users should see JSON schema support for
hxformat.json files, giving them suggestions and autocomplete when editing formatter settings.
Also if people were having issues where formatter would “eat” or destroy their code, version 1.3.0 has a new safeguard that should detect and prevent such behaviour. Formatter should skip formatting a file before destroying your code (better no formatting than destructive formatting).
If you have samples where formatter fails to format or destroys code, please open an issue on github (https://github.com/HaxeCheckstyle/haxe-formatter).