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
If you have components in your package which extends classes from different external packages and the external packages have classes with the same names and folder structures all members, attributes,... are mixed in to the declarations of your component.
This is because the inheritance applier in the post processing phase is not including the npm package in to the checks while building up the inheritanceChain.
I prepared a fixture to explain the problem in detail here.
Expected behaviour
The inherited members should be the ones from the imported classes and not a mix of all classes with the same name.
The text was updated successfully, but these errors were encountered:
If you have components in your package which extends classes from different external packages and the external packages have classes with the same names and folder structures all members, attributes,... are mixed in to the declarations of your component.
This is because the inheritance applier in the post processing phase is not including the npm package in to the checks while building up the
inheritanceChain
.I prepared a fixture to explain the problem in detail here.
Expected behaviour
The inherited members should be the ones from the imported classes and not a mix of all classes with the same name.
The text was updated successfully, but these errors were encountered: