added prettier.io as an experiment for code formatting

[reusr1]

• code style format through prettier*

as an alternative to #189 I tried to use prettier (using their defaults)

npx prettier --write .

observation: if you run percli hatch "*" we of course revert a lot of code back to a style that is not desired

[cmrockwell]

This PR seems to have the outcome of standards applied committed along with the added config file .prettierrc.json
It would be nicer to commit the changes to the build and new files like .prettierrc.json separated from the work of applying the standards. Maybe something like https://github.com/HubSpot/prettier-maven-plugin ?

[reusr1]

This PR seems to have the outcome of standards applied committed along with the added config file .prettierrc.json
It would be nicer to commit the changes to the build and new files like .prettierrc.json separated from the work of applying the standards. Maybe something like https://github.com/HubSpot/prettier-maven-plugin ?

@cmrockwell the PR was mostly to illustrate the result of prettier.io and if that would be acceptable by others or if we want to use what @Felix-Puetz proposed in #189

[reusr1]

looking at the conflicts and the output a bit more it seems we first have to fix the output from our code generator to work better with enabling prettier.io

also wondering if we should move to 2 spaces instead of 4 for the tabs

[flx-sta]

Why don't we just start with something?`and keep on going from there.
It's just code-format..