Set explicit rules about naming convention

[OlivierAlbertini]

Is your feature request related to a problem? Please describe.
PR review should not need to check naming convention as it should be caught by CI.

Here an existing package: https://www.npmjs.com/package/tslint-consistent-codestyle#naming-convention

I will check if newer tslint version does already this...

"naming-convention": [true,
{"type": "method", "modifiers": "protected", "leadingUnderscore": "require"},
{"type": "member", "modifiers": "protected", "leadingUnderscore": "require"},
{"type": "member", "modifiers": "private", "leadingUnderscore": "require"},
{"type": "enumMember", "format": "PascalCase"},
{"type": "property", "modifiers": ["static"], "format": "UPPER_CASE"}
]

This is an example. Don't hesitate to add your requirements by adding a comment

Describe the solution you'd like
We should explicitly add rules for naming convention

We should start after #106 (review) is merged

[danielkhan]

@OlivierAlbertini - SGTM. Would you be open to take this one and provide a PR?

[OlivierAlbertini]

@OlivierAlbertini - SGTM. Would you be open to take this one and provide a PR?

Sure