libsass-maven-plugin VS spotless

The first way would be to configure Maven (or whatever build-tool you are using), so that it compiles the files to CSS while compiling the whole Java-Program. There are multiple librarys for that, the best one (at least from my point of view) being this one . There are other projects, that try to do the same, like described in this blog post. However, there is a problem with this approach: to make the Scene-Builder work properly, the CSS actually needs to be compiled before runtime. That means, it has to happen on the fly, as soon as we make a change in our files.

Spotless is an open-source, multi-language, customizable code formatter for projects. It comes with a Maven Plugin that can be customized as needed.

Some code formatters such as Spotless (https://github.com/diffplug/spotless/tree/main/plugin-gradle...) allow you to format code only in files that have changes against some designated branch such as `master`. So, you check out your feature branch, make changes, do some commits, and run spotless. Only the files which have some changes between your workspace and the master branch will be formatted. This allows you to gradually format the project as and when files would be changed anyways.

As a Top-Level Apache open source project, ShardingSphere has 400 contributors as of today. Since most developers do not have the same coding style, it is not easy to standardize the project’s overall code format in a GitHub open collaboration model. To solve this issue, ShardingSphere uses Spotless to unify code formatting.

But please just use an code formatter like spotless. Or better yet set it as a pre commit hook. You will thank yourself later, and so will all of your coworkers.

I use Spotless but it’s not as opiniotated as Prettier or Black

I use Spotless and it works quite well, but there are many other options. Also good IDEs can reformat your code.