Alex Lohr
Alex Lohr
Interestingly, the cookie is internally utf-8, but the header that the browser sends seems to already have the wrongful encoding. From the localhost:3000 request header: ``` cookie: umlauts="öäüÖÄÜ" ```
Interestingly, this is actual browser behavior. A few RFCs tried to rectify the situation, but still aren't supported by most major browsers. I guess I have to encode the cookie...
Sorry for the delay, my attempts to make \u... escapes failed and the solution became too complex, so I had to pivot to use encodeURIComponent - but then, cookies are...
We could still provide an additional wrapper if we find more applications that have the same use case. I wouldn't want to increase the bundle size of existing apps because...
Strange. I used the "edit this" link from the page. What would be the correct folder then?
I like the idea of a `resolveTags` helper. Not being type safe may be a drawback, but not one that should concern us. We should use a callback function that...
Dynamic components are not yet supported like this IIRC. You would need to use Dynamic, but otherwise, it illustrates well what is meant.
Ah, then that's already fixed, it seems.
The issue here is that setState has to accept partials, since those are merged with the current object. We cannot constrain the types more without breaking that ability.
The name events easily lends itself to confusion with UI Events. What you implement here is a message bus, not an event system.