Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inheritance for 'attributes' and 'members' are merged from the wrong class files. #296

Open
veith opened this issue Feb 21, 2025 · 0 comments · May be fixed by #297
Open

Inheritance for 'attributes' and 'members' are merged from the wrong class files. #296

veith opened this issue Feb 21, 2025 · 0 comments · May be fixed by #297

Comments

@veith
Copy link

veith commented Feb 21, 2025

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.

@veith veith linked a pull request Feb 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant