When a JSII interface has a name like `IFoo`, the generated .NET interface is named `IIFoo`

[mpiroc]

We should detect the case where the interface already has the I- prefix, and skip adding an additional I- prefix in this case.

Open question: What if the interface is named something like IAMFoo? I.e. it begins with I<capital letter>, but the I isn't intended as a prefix.

[assyadh]

After talking with Romain, we chose to:

Not prefix with I anymore for interfaces that are NOT datatype (jsii already enforces that non-datatype interfaces have a name prefixed with the I). Only datatype interfaces should append an I.

[eladb]

Do we really need interfaces for data types? I was under the impression that in .NET we can express these data types without interfaces.

[assyadh]

See my comment here:

https://github.com/aws/jsii/blob/master/packages/jsii-pacmak/lib/targets/dotnet/dotnetgenerator.ts#L148

Right now for each interface we create the interface, the interface proxy and the interface datatype class (implementing the original interface).

In the case of a datatype (props), we could do with JUST the datatype, not implementing any interface.

Relates: #480

Given that props objects are datatypes, they would live by themselves.

[eladb]

So if I understand correctly the answer is that we can get rid of interfaces for data types (formally known as “structs”). Correct?

[assyadh]

Yes

[fulghum]

@assyadh – so the work for this task now, is just to remove the generation of interfaces for struct/data classes?