Fork me on GitHub
#fulcro
<
2020-01-15
>
thosmos07:01:29

whenever I load my app I get timeouts on all my routers. Is this normal?

DEBUG [com.fulcrologic.fulcro.ui-state-machines:?] -  TIMEOUT on :riverdb.ui.root/TopRouter due to timer :error-timer after 5000 ms
DEBUG [com.fulcrologic.fulcro.ui-state-machines:123] -  Triggering :timeout! on :riverdb.ui.root/TopRouter with {}
WARN [com.fulcrologic.fulcro.ui-state-machines:?] -  UNEXPECTED EVENT: Did not find a way to handle event :timeout! in the current active state: :routed
DEBUG [com.fulcrologic.fulcro.ui-state-machines:?] -  TIMEOUT on :riverdb.ui.theta/ThetaRouter due to timer :error-timer after 5000 ms
DEBUG [com.fulcrologic.fulcro.ui-state-machines:123] -  Triggering :timeout! on :riverdb.ui.theta/ThetaRouter with {}
WARN [com.fulcrologic.fulcro.ui-state-machines:?] -  UNEXPECTED EVENT: Did not find a way to handle event :timeout! in the current active state: :routed
DEBUG [com.fulcrologic.fulcro.ui-state-machines:?] -  TIMEOUT on :riverdb.ui.sitevisits-page/SVRouter due to timer :error-timer after 5000 ms
DEBUG [com.fulcrologic.fulcro.ui-state-machines:123] -  Triggering :timeout! on :riverdb.ui.sitevisits-page/SVRouter with {}
DEBUG [com.fulcrologic.fulcro.ui-state-machines:?] -  Activating state  :failed on :riverdb.ui.sitevisits-page/SVRouter

tony.kay15:01:17

@thosmos no. sounds like some kind of bug.

tony.kay16:01:14

I’ve released 3.1.5-SNAPSHOT on clojars with a fix to a subtle input problem: If a key is removed from the props of an input, it does not disappear. I’ve verified that this new version fixes that problem, and that inputs still seem to work correctly (including the infamous cursor jump bugs with async updates). It was a very minor patch, so I do not expect problems, but since it affects form inputs I would love it if various ppl would test it out as a sanity check. I’m using it in my production development as a preliminary test myself.

metal 4
fulcro 16
tony.kay16:01:38

Thanks to @codonnell for the report and suggested fix, and to @thosmos for some additional thoughts/suggestions.

tony.kay16:01:13

So, I just got a message from GitHub Sponsors about the first payout, and it is nearly $1500 (accumulated over the past 4-6 months, I think). Many contributions have also come in over the past few years from Patreon. While it isn’t a ton on a per-hour basis (OSS work pays waaay below minimum wage), it was still a nice surprise, and I wanted to express some gratitude to the community that has supported the project with financial donations. Thank you. Anyone interested in helping that way should definitely check out https://github.com/sponsors/awkay. GitHub sponsors still has donation matching, so your contribution goes twice as far right now! I’d also like to thank everyone that has been supporting Fulcro in non-financial ways: Thanks to @wilkerlucio for his great work on Pathom, EQL, and Inspect. Appreciation goes out to @thheller for giving us a build tool that makes using CLJS such a pain-free development experience, and to the work @cfleming does in maintaining Cursive. Fulcro would not be anywhere near as good as it is without the environment around it being so great. I also appreciate the people are jumping in with PRs, documentation fixes, etc. It all helps.

🚀 32
😎 16
❤️ 36
🎉 16
tony.kay17:01:20

Updated book with docs on the new ide-navigable routing via path-to: http://book.fulcrologic.com/#CodeNavigableRoutes

👍 4
thosmos23:01:42

This is great! Something similar could be href-to that could be used like (dom/a {:href (dr/href-to RootComp SubComp {:arg 1})}) Would also be nice to just be able to do (dr/route-to! RootComp SubComp {:arg 1})

tony.kay01:01:54

Yes, a function that combines them would be good..simple enough to write

otwieracz22:01:53

What am I doing wrong?