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
It is not idiomatic TypeScript to prefix interfaces with I (See here and here, an in general, any of the types from @types), and so on creation of this codebase, I didn't carry over the usage of I prefixed interfaces in general from the internal codebase it is based on.
As documented, I did retain I prefixes for a special meaning - as a way to indicate interfaces that can be overridden by plugins.
Some recent additions used the I prefix for non-pluggable interfaces. Let's discuss, so that the codebase remains consistent.
The text was updated successfully, but these errors were encountered:
It is not idiomatic TypeScript to prefix interfaces with
I
(See here and here, an in general, any of the types from@types
), and so on creation of this codebase, I didn't carry over the usage ofI
prefixed interfaces in general from the internal codebase it is based on.As documented, I did retain
I
prefixes for a special meaning - as a way to indicate interfaces that can be overridden by plugins.Some recent additions used the
I
prefix for non-pluggable interfaces. Let's discuss, so that the codebase remains consistent.The text was updated successfully, but these errors were encountered: