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
When m.route is called for null root, the modules are initialized, but nothing is rendered (without any errors or warnings). I just encountered this when passing non-existent document.body and it took some time to figure out the "root" of the problem (pun intended). This problem may occur in case of a typo or if you use the element before it has been parsed (yes, a newbie's error).
So I was wondering. Is there a case when null root is desired? If no, then shouldn't Mithril warn about such faulty usage?
The text was updated successfully, but these errors were encountered:
When
m.route
is called for null root, the modules are initialized, but nothing is rendered (without any errors or warnings). I just encountered this when passing non-existentdocument.body
and it took some time to figure out the "root" of the problem (pun intended). This problem may occur in case of a typo or if you use the element before it has been parsed (yes, a newbie's error).So I was wondering. Is there a case when null root is desired? If no, then shouldn't Mithril warn about such faulty usage?
The text was updated successfully, but these errors were encountered: