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
Is is hard to persuade developers with C# background to name interfaces without I prefix. The following "Why" could be helpful: Naming interfaced without I forces developers to give proper name to abstraction and concrete implementation, emphasizing their differences e.g. SportsCar->Car, SuvCar->Car vs just Car->ICar.
Please add it to ng2 style guide.
The text was updated successfully, but these errors were encountered:
I dissagree on not naming interfaces with an I, because when you just see the code files, you can't tell if it's an interface or not...... The I is very helpful here! It has nothing to do with not being able to name the actual abstraction, @stasberkov, it's all about code readability.....
Is is hard to persuade developers with C# background to name interfaces without
I
prefix. The following "Why" could be helpful: Naming interfaced withoutI
forces developers to give proper name to abstraction and concrete implementation, emphasizing their differences e.g.SportsCar->Car
,SuvCar->Car
vs justCar->ICar
.Please add it to ng2 style guide.
The text was updated successfully, but these errors were encountered: