Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AOT: Inherited lifecycle callbacks are not called

See original GitHub issue

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting

Current behavior Lifecycle callbacks do not depend on metadata, thus it is separate issue. See comment.

Expected behavior Inherited lifecycle callbacks should be called.

What is the motivation / use case for changing the behavior? There are several reasons to use inheritance:

automatic clearing of rxjs subscriptions
automatic removal of listeners
adding common initialization code
… and others

Angular version: 2.0.1
Language: [all]

Issue Analytics

State:
Created 7 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

4reactions

kemskycommented, Oct 10, 2016

While decorators and metadata may need special rules for inheritance, i believe that rules for method inheritance are already well defined and can not be altered. Also it is an AOT issue, so plunker is not possible. This is also reflected in ticket title: Proposal: Support well-defined rules of inheritance for Angular decorators.

3reactions

zoechicommented, Oct 10, 2016

It’s an inheritance issue and they are tackled together at 11606 so I don’t see a problem with closing this issue. Your issue also doesn’t contain a Plunker and not even code that demonstrates the problem.