Currently eslint config is pretty loose, which is good. But for best practice and consistency eslint should enforce accessibility modifiers to tell us developers to really think what we are doing and trying to achieve. We are aware that traditional TypeScript accessibility modifiers (public, private, protected) do not enforce accessibility control at runtime. However TypeScript does enforce accessibility modifiers during type-checking phase. In addition to that eslint should also show up basic stuff like unsused imports and relative import paths (should be absolut). Therefore eslint should be a little more strict at this point .
Motivation
Currently eslint config is pretty loose, which is good. But for best practice and consistency eslint should enforce accessibility modifiers to tell us developers to really think what we are doing and trying to achieve. We are aware that traditional TypeScript accessibility modifiers (public, private, protected) do not enforce accessibility control at runtime. However TypeScript does enforce accessibility modifiers during type-checking phase. In addition to that eslint should also show up basic stuff like unsused imports and relative import paths (should be absolut). Therefore eslint should be a little more strict at this point .
Acceptance criteria
Technical solutions
/
Attachments
/