Matt McCray

:+1: This would be spectacular!

Here's a patch showing what I'm currently doing: ``` patch From 3d11fedf2ac76aa6a319486e43029ffd144bd5ba Mon Sep 17 00:00:00 2001 From: Matt McCray Date: Mon, 7 Oct 2013 17:07:37 -0500 Subject: [PATCH] Added...

@Railk Thanks!

It's definitely tricky. Just my two cents: - Route change handlers could be registered at the route level -- Either via the `` component or from the `useRoute()` hook. -...

Is this a serious bug, or is it a "safe to ignore bug," like some that React reports?

It appears to be in the `view` hoc for *function components*. If you convert components in the example codesandbox to class components, the warning goes away. https://codesandbox.io/s/errors-with-react-easy-state-forked-8yqc1?file=/src/App2.js

Is there really no better solution than the abomination of *Captcha? Serious question, not just a vent.

Those are all things I'd love to see done. :smile: Especially 4 & 5. Also, `etc/strftime.js` should move to a node-friendly (and small of size) replacement. Also also, make sure...

Yeah, I'm all for that. I'd go with strftime, moment too heavy for this use IMO.

If I recall correctly, that was for older IE browsers. I'm not sure if it's really necessary anymore or not. I'd say if it passes on IE9+, then it's good....