NullVoxPopuli

Thank you for the reproduction, I've put it all in a gjs file over here: https://github.com/NullVoxPopuli/repro-destruction-tracking ```gjs import Route from 'ember-route-template'; import { Labelled } from './components/labelled'; import { tracked...

What's interesting is that if I remove the middle component, both 5.5 and 5.6+ error ```gjs import Route from 'ember-route-template'; import { Labelled } from './components/labelled'; import { tracked }...

Good news -- switching to `@glimmer/component`, and using `registerDestructor` via: ```js constructor(...args) { super(...args); registerDestructor(this, () => { this.args.incrementWillDestroy(); }); } ``` is a good way to migrate away from...

It does, ya. And is async, so it would avoid the problem altogether (Sync destruction is the problem here, so i don't think we have a bug)

I think the bug is that it ever worked at all

fwiw, folks should be migrating away from render-modifiers. It was only meant to be a temporary migration tool around the 3.16 era. There is both a template-lint and eslint lint...

I suppose this could be fixed if decorators can set the type of the field. Since decorators can add an initializer, it kinda makes sense that a decorator could define...

> Why is it renderComponent() ... when it renders a template? > There is plenty API that adressess templates, but this is also very much fragmented. Can we all the...

> A good question brought up by @void-mAlex at RFC review: what happens if you call renderComponent multiple times with the same Element? Is that allowed? update pushed!

Clarification has been added around the calling-multiple-times-on-the-same-element behavior, and during the RFC review meeting, since FCP is passed, we decided to merge -- I'll now head over to implementing --...