Add settings and info for developing UI in IntelliJ

[aaronweissler]

This change is 

[PDuwe]

Some tests seem to be failing.

Also, you could still get rid of the warnings. Looks good apart from the tests however, so you decide :)

[aaronweissler]

Some tests seem to be failing.

Those agent tests have been failing seemingly randomly for a small while now. We still will investigate that further, but it's definitely not related to this PR, since there are no changes to Java code or directly related things in here at all (which also was my motivation for adding additional ignore paths for the workflow in #1497 that you also reviewed ^^)

Also, you could still get rid of the warnings. Looks good apart from the tests however, so you decide :)

If you mean the warnings seen in Files Changed, they are also not related to this PR's changes, I'm not sure why GitHub is showing them for those two files.

[heiko-holz]

Reviewed 4 of 4 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @aaronweissler and @PDuwe)

---

CONTRIBUTING.md line 17 at r2 (raw file):

### Frontend Developing
If developing JavaScript in IntelliJ, check that Settings.Languages & Frameworks.JavaScript.Code Quality Tools.ESLint is activated for correct linting.

this feature is only available in IntelliJ Ultimate, right?

If so, please add Ultimate

---

components/inspectit-ocelot-configurationserver-ui/.eslintrc line 45 at r1 (raw file):

        "import/no-useless-path-segments": "error",
        "react/prop-types": "warn",
        "prettier/prettier": ["error", { "endOfLine": "auto" }]

this fixes the delete 'CR' [prettier/prettier] error message, right? (https://stackoverflow.com/questions/53516594/why-do-i-keep-getting-delete-cr-prettier-prettier)

---

components/inspectit-ocelot-configurationserver-ui/README.md line 33 at r2 (raw file):

And the following to fix them automatically.
```bash
yarn format:write

what does yarn format:write do as compared to yarn lint --fix?

Is it recommended to run eslint --fix on save?

[heiko-holz]

components/inspectit-ocelot-configurationserver-ui/README.md line 33 at r2 (raw file):

Previously, heiko-holz (Heiko Holz) wrote…

what does yarn format:write do as compared to yarn lint --fix?

Is it recommended to run eslint --fix on save?

(addendum: with current version of IntelliJ, we can use Tools.Actions on Save and check Run eslint --fix:

[aaronweissler]

Reviewable status: 2 of 4 files reviewed, 2 unresolved discussions (waiting on @heiko-holz and @PDuwe)

---

CONTRIBUTING.md line 17 at r2 (raw file):

Previously, heiko-holz (Heiko Holz) wrote…

this feature is only available in IntelliJ Ultimate, right?

If so, please add Ultimate

Yes, you're right. Done.

---

components/inspectit-ocelot-configurationserver-ui/.eslintrc line 45 at r1 (raw file):

Previously, heiko-holz (Heiko Holz) wrote…

this fixes the delete 'CR' [prettier/prettier] error message, right? (https://stackoverflow.com/questions/53516594/why-do-i-keep-getting-delete-cr-prettier-prettier)

Yes, exactly, and, as far as I understand, git takes care of keeping the correct line endings in the repository, so it's okay to accept the Windows line endings locally.

---

components/inspectit-ocelot-configurationserver-ui/README.md line 33 at r2 (raw file):

Previously, heiko-holz (Heiko Holz) wrote…

(addendum: with current version of IntelliJ, we can use Tools.Actions on Save and check Run eslint --fix:

yarn format:write runs prettier --write fixing issues, while yarn lint --fix or yarn lint:fix run eslint --fix. So in this case it should be the lint command instead. If I understand correctly, the lint command also considers errors considered by prettier anyways.
I also like just using the auto apply, so you get your errors fixed while developing without having to think of running it yourself, and don't have to fix all of them at once in the end if you forget.

[heiko-holz]

Reviewed 1 of 2 files at r3.
Reviewable status: 3 of 4 files reviewed, all discussions resolved (waiting on @heiko-holz and @PDuwe)

---

components/inspectit-ocelot-configurationserver-ui/README.md line 33 at r2 (raw file):

Previously, aaronweissler wrote…

yarn format:write runs prettier --write fixing issues, while yarn lint --fix or yarn lint:fix run eslint --fix. So in this case it should be the lint command instead. If I understand correctly, the lint command also considers errors considered by prettier anyways.
I also like just using the auto apply, so you get your errors fixed while developing without having to think of running it yourself, and don't have to fix all of them at once in the end if you forget.

Thanks for the explanation!

[heiko-holz]

Reviewed 1 of 2 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @PDuwe)