Is there a naming convention for TypeScript interfaces?
TypeScript provides interfaces that are used for two main reasons:
Standardize/ Giving a type to an object, by defining the properties that an object contains.
Define a structure of properties and/ or functions that a class has to implement. Doing this way you can define multiple implementations that implement the interface. In this case, the interface works as a contract (known best practice term from C#) that the classes have to respect.
So now the question is, how should you name your interfaces? Should you use the “I” letter at the beginning of the name of the interface or not?
When the purpose of your interface is the first point from the previous list, then I can understand if you choose not to use the “I” letter. But if you use an interface as a contract for a set of relevant classes, then I use the “I”-naming convention and I suggest you doing the same. Here are some advantages of doing so:
By looking on the name of the file you can directly understand if the file contains a class or an interface, without having to open the file to find it out. Apart from that you can also gather your TypeScript interfaces into a folder (possible names could be “Definitions”, “Contracts” or “Interfaces”) so that you do not mix them with the files that contain your classes.
Coming from the C# world is easier for you to adapt to this convention, since you already used it like hundred times.
When naming the classes that implement an interface you can simple remove the “I” letter from the name of the interface, leave the remaining intact and just add at the beginning the words that uniquely identify your class.