Enforce better naming convention

[isBatak]

Solves #42 and #44

What's the best way to test these changes?
This issue #42 (comment) may still exist.

Todo

• add test after this is merged Core js tests #80

[fvoska]

To test the changes, it is best to create an example project that uses the config and write some code that would trigger linting errors/warnings. That is how we did it for Angular-specific eslint config here and we could probably do the same for the base TS config with some simple TS example project

[fvoska]

As for the issue from the comment #42 (comment), I had the same issue on some angular repo where I added some 3rd party rule that require TS compiler and there I also had to define parserOptions.project (https://github.com/infinum/ngx-nuts-and-bolts/blob/main/libs/ngx-nuts-and-bolts/.eslintrc.json#L8). I think this is something that will have to be done in each project individually because the tsconfig file that we have to point to might be in a different location or named differently.

We should update the readme with this info.

[kristijanbambir]

Is this PR done or is there more work to be done? If it's not done, please convert it to a draft until completed.

[adrianbicanic]

@isBatak Any updates or info related to this PR?

[isBatak]

@adrianbicanic I have to revisit this PR and add tests

[isBatak]

@adrianbicanic it's ready!

[kamdubiel]

Done in:
#128