Managing Interface correctly in FamixNG about famix HOT 4 CLOSED

Is this issue still relevant, since we added Interfaces in Java?

from famix.

The reason for isInterface is the logic in the subclasses. For example, those that deal with generics. Of course, now with traits, you might have a better reusability mechanism, but do take a look at the subclasses.

from famix.

FamixInterface seems OK to me (you'd want to see all the interfaces in a design), since the entity is only that. But I'm not sure of the added value of FamixImplementation (because implementations can be for several interfaces) vs a classic FamixClass that has a relationship of implements to one or many FamixInterface entities.

@girba without a concrete example, I don't understand about subclass logic with interfaces (generics is not my strong point).

I found this discussion because I didn't understand how isInterface was generated in the FamixJava model. But now, thanks to @NicolasAnquetil, I know it is/was hard-coded in the Entities. So, maybe this comment is off topic, but I almost expected a FamixJavaClass to use a TCanBeInterface trait which has the isInterface property (similar to how isAbstract works for classes with TCanBeAbstract).

In our FamixTypeScript MM it would be useful to say classes are related to an interface trait. Since this kind of "interface" can exist in C++/Java/C#/TypeScript/Pharo/... a trait would definitely be useful as an abstraction.

from famix.

close with #443

from famix.