Closed akarnokd closed 7 years ago
I guess that makes sense, to be consistent with the names of actual interfaces.
Not a fan of this naming scheme, but I guess it is really embedded deeply in the .NET ecosystem right?
really embedded deeply in the .NET ecosystem right
Yes, Visual Studio even adds a small squiggly line if an interface definition doesn't start with I
.
Perhaps adding a note that they correspond directly to the "Publisher" and friends in RS?
Not sure about this, not many developers are criss-crossing between C# and Java and not recognize the matching between the interfaces.
This PR adds the
I
prefix to mentions of the component names to be consistent with the code examples.