Talin

Alternatively, don't register preferences at all, instead register loaders. That is, you have some trait `PreferenceLoader`, analogous to `AssetLoader`, and you have a registry of impls of these. The loader...

I think that this PR is punting on too many things and isn't opinionated enough. The problem with "leaving things up to the developer" is that it risks each crate/plugin...

I think that we should get some clarity on the design before committing this, possibly via an RFC. While a working prototype has the advantage of easily attracting contributors, if...

Let me offer an alternative proposal for a preferences API: * Each preference item is a `Resource`. * There is a resource named `Preferences` which looks like: ```rust struct Preferences(HashSet);...

@aevyrie @cart @inodentry Let me sketch out a possible synthesis of these approaches: preferences as resources or plugin state. My assumption is that preferences are ordinarily something that is read...

Always happen to help out with word-smithing, but I generally don't like to volunteer to write a complete doc until I know roughly the shape of what's going to be...

The other three issues are about solid.js - only this one pertains to solid-start. I didn't realize that there were separate doc projects.

@nksaraf As a general rule, there should be no coupling between the tsconfig strictness of a library and the strictness of the code that uses that library. The solution is...

I eventually worked around this problem by post-processing the object to covert all the objects in the response to have normal prototypes.

Based on the Discord chat from a few weeks ago, I think Ryan might have added a fix for this but I am not sure.