Ethan

I couldn't see how this is supported on the `master` branch as of now. (Am I missing something staring me in the face?) However, in the meantime, I've come up...

@vadimdemedes Sorry I missed your reply - an unnoticed bad filter started filtering my GH notifications incorrectly. Here's a code sample of the problem I'm trying to address: ```(typescript) import...

Using that approach has a couple of issues: 1. It causes multiple renders. Ink renders the layout once (so before `useEffect` has been triggered) w/o any data on width/height. `useEffect`...

The former isn't an issue since you're already creating a separate Jinja Environment strictly for Lovelace Gen, (`jinja = jinja2.Environment(loader=jinja2.FileSystemLoader("/"))`) so any custom symbols would be limited only to Lovelace...

I seem to be hitting this on a Nest Hub as well. Any new developments or findings in the last month?

https://github.com/ostinelli/net-http2/pull/47

@phiresky The spec has been revised - `addinitializer` was added to `field` decorators for consistency, but, yeah, it looks like the README in the GitHub repo has not been updated...

@Obi-Dann I've been out of the MobX code base for a bit, but from a JS stand point, field decorators cannot augment the value of the field. They're annotation only....

@urugator If there were tests for such for legacy decorators - yes. I pretty much just duplicated the whole decorators test file and ported it to use 2022.3 decorators.

(Implementation note/context - not really an answer) This is a little tricky with the 2023.x decorators spec. Getters and Setters may now have separate decorators applied to them - it's...