You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Old proposal
I'm collecting things for a potential FAQ page. I've got a few already, but I know there's got to be more between here and Gitter. This would include both TS-related and core Mithril-related stuff, so we have an easy, always-up-to-date page on commonly asked questions here.
What vnode.state is in various places, including in the various component types as well as in the vnode attrs themselves - this is probably second only to routing in its complexity, and it's tripped people up more than once.
What vnode.state is in various places, including in the various component types as well as in the vnode attrs themselves.
We need to show people how to install the typings and show them where to report typings issues. This hasn't shown up in the GH issues much, but many people have asked on Gitter where they are. It's not exactly obvious from the mithril.js.org website that we generally support them as a community-maintained thing, and I think we should fix that.
The text was updated successfully, but these errors were encountered:
@MithrilJS/collaborators I can't be the only one noticing patterns here with common questions. I plan to drop this by the Mithril Gitter, too, to see if I can get some more things to potentially add. I'm pretty sure we could get a pretty decently sized page of various frequently asked questions in various areas.
dead-claudia
changed the title
Add a FAQ page
Missing documentation on some core stuff
Sep 1, 2018
Edit: Not suggesting adding a FAQ page anymore, so I recast the issue. I've preserved the previous text in case you're curious what it was previously.
Old proposal
I'm collecting things for a potential FAQ page. I've got a few already, but I know there's got to be more between here and Gitter. This would include both TS-related and core Mithril-related stuff, so we have an easy, always-up-to-date page on commonly asked questions here.vnode.state
is in various places, including in the various component types as well as in the vnode attrs themselves - this is probably second only to routing in its complexity, and it's tripped people up more than once.Why we include almost everything - the excess isn't really as much as you might thinkA conversation with @barneycarroll reminded me this isn't quite set in stone enough to be on a FAQ page as a canned answer.There's a couple things I've found that need documented, and I'm pretty sure there's more that also need added.
vnode.state
is in various places, including in the various component types as well as in the vnode attrs themselves.The text was updated successfully, but these errors were encountered: