Fore code that can be called externally (or public so to speak) I think it makes sense to document methods etc.
I tried to enable it only on exported members (by setting publicOnly to true).
But the plugin doesn't seem to be detecting some cases as exported:
an interface that is not directly exported with export interface Foo but only exported at the end with export {Foo}
an interface that is implicitly exported because its used in a function.
So I decided to set publicOnly to false for now. I assume most of the code in those utils will be public anyways.
But for me it's also okay if developers manually use eslint-disable for stuff that is not public.
@drebrez
Fore code that can be called externally (or public so to speak) I think it makes sense to document methods etc.
I tried to enable it only on exported members (by setting
publicOnly
totrue
).But the plugin doesn't seem to be detecting some cases as exported:
export interface Foo
but only exported at the end withexport {Foo}
So I decided to set
publicOnly
tofalse
for now. I assume most of the code in those utils will be public anyways. But for me it's also okay if developers manually useeslint-disable
for stuff that is not public.