You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
although tslint is introduced in Formatting, since most tslint rules do not override interface-over-type-literal and are true, contents of type vs interface will error .
(confirming, only TSLint Clean Code was false)
also issues, it may be deleted from tslint: recommended in future, but it has not disappeared at moment.
Important thing is that if you follow the rules of tslint, will most likely result in an error.
need to set interface-over-type-literal to false as a workaround, should prompt for a trade-off with quality.
should I add this as a supplement to type vs interface?
The text was updated successfully, but these errors were encountered:
There might be more options like interface-over-type-literal that are not inline with principles from Clean Code. We should try to avoid transforming this tutorial in a TSLint guide.
And after all, TSLint is introduced as a recommendation and example of tools that can help make your code clean.
There might be more options like interface-over-type-literal that are not inline with principles from Clean Code. We should try to avoid transforming this tutorial in a TSLint guide.
And after all, TSLint is introduced as a recommendation and example of tools that can help make your code clean.
Okay I agreed !
I will contributing project according to that policy in future.
Thank you for answer!
although tslint is introduced in Formatting, since most tslint rules do not override
interface-over-type-literal
and aretrue
, contents of type vs interface will error .(confirming, only TSLint Clean Code was
false
)also issues, it may be deleted from
tslint: recommended
in future, but it has not disappeared at moment.Important thing is that if you follow the rules of tslint, will most likely result in an error.
need to set
interface-over-type-literal
tofalse
as a workaround, should prompt for a trade-off with quality.should I add this as a supplement to type vs interface?
The text was updated successfully, but these errors were encountered: