Jan Buschtöns

Just updated Atom to v1.17.0 and experienced the same issue. Then I updated all packages and restarted Atom. The issue was resolved then.

Interesting. I'm also using Material Dark.

@tonycoco @ebryn Regarding the `style=""` injection: I'm no expert, but it sounds like this would degrade performance. But as long as this is only _one possible_ mode of many, I...

> I believe most of the Ember core team believes Sass is the preprocessor we should focus our support on I would also like to know, why you've come to...

:+1: I think there was a discussion about properly pluggable blueprints for ember-cli.

We're also _extremely_ interested in this, but so far only did some thought experiments. I guess that it will only really / sustainably be possible, once ember-engines uses embroider under...

We could also make use of this in Ember's `Application` class `rootElement` property. Some questions that popped up for me, not sure, if in scope though: What if a descriptor...

I would also prefer not mutating the host object. @rwjblue's `getCachedValue(host, key)` from https://github.com/emberjs/rfcs/pull/656#issuecomment-675743985 looks great to me. Due to the synchronous, single-threaded nature of JS we _could_ even make...

One issue I see with the extra `@cacheFor()` decorator is TypeScript support. The property type could not be inferred, so users need to explicitly type it, whereas `getCachedValue(host, key)` could...

I still think that either exposing the low-level `createCache` and `cacheGetValue` functions or a `getCachedValue` function is superior. It would allow you to very easily build a `@cacheFor` decorator on...