Encourage decentralizing the template registry for Ember projects

[dfreeman]

While the centralized registry approach is nice in that it's something we could more easily automate generating, it really doesn't play nicely with TS's internal dependency tracking and cache invalidation, leading to some bizarre behavior with glint --watch and, I discovered more recently, glint-language-server if you don't happen to have the registry document open in your editor.

For now, we can instead suggest augmenting the registry inline in each module that exports a template entity. Aside from avoiding the invalidation errors, this also has the nice side effect of bringing you to the actual source module when you go-to-definition from a template.

[jamescdavis]

That's interesting about the centralized registry not playing nice with TS's dep tracking and cache invalidation. TBH, this approach feels more natural to me when populating the registry manually (which is why I did it with these demo components originally 🙂 ). I guess it's all those years of adding ember-data models to the registry at the bottom of each. I do like that go-to-def always gets you to the right file with this approach.

[chriskrycho]

👍🏼