Franklin Ross

In fact this seems true for pretty much any collection like `IDictionary`, or even `IEnumerable`. Is this by design? I've been creating `ScriptableObjects` that implement these so I can share...

I tried using `SharedInstance`, as that seems to be the FullInspector way to do what I'm trying, but I get compile errors in the generated shared instance file: ``` [SerializeField]...

This is true. Personally I love it when I don't have to go to TSD as the definitions often seem to lag. There are also less steps involved when assessing...

Yeah I did see that solution in one of the other issues. I just think it'd be easy and clear to add this kind of thing to the API as...

Hmm. Well, maybe it is reasonably obvious and I'm just being pedantic 😜 On Wed, 22 Jul 2015 10:10 pm Franklin Ross [email protected] wrote: > Yeah I did see that...

Yeah OK. I've never actually created a pull request for GitHub before, but have been meaning to learn for a while. Better late than never ;-P Give me a few...

Yeah, fair enough. I guess I figured a best effort is better than nothing when `conditions` isn't provided? Otherwise, it straight up doesn't work for 100% of the cases prior...

Or even just a handful of common pre-configured ones and a little documentation, like "for Node based tests, do `'resolver': 'jest-node-exports-resolver/node'` or something. I dunno, just trying to think of...

I think I have this same issue. I'm issuing a rebuild of my CSS files in the `finishModules` hook so I can narrow down the set of files that Tailwind...

When I was debugging this, I noticed there are 2 very similar CSS modules (as in Webpack modules in the compilation) for each actual CSS file in the dependency tree....