Gilbert
Gilbert
> Code examples can use destructuring syntax by now You have to be careful where you destructure: ```js // Good function Foo(ctx) { return () => { let { attrs...
> If we go the context route, I'll also be pushing to add `context.state` and `context.link` as explained above, which will completely avoid the closure problem by...just not using closures...
> Caught this in Gitter: Providing ctx to both is a great solution IMO. And to add and comment on the conversation, @barneycarroll writes: > Personally Iād avoid lifecycle entirely...
Any updates on this? Very interested in getting both-side rendering in mithril.
IMO a better interface design would be tagged template literals. That way you can interpolate values and Tau would know how to convert them into internal representations: ```js let num...
Yes!! š
For the record, I implemented this locally, and it's working beautifully. Here's the patch: json-unify-grounded-keys.patch ```diff commit b31e0e23978c396d656c22596a83650899cc67bf Date: Thu Mar 10 22:00:15 2022 -0600 Implement simple version of tau-prolog/issues/295...
Wonderful! š I will try this out in the next couple weeks.
I haven't implemented it. Glad you like it!
Ok, so I implemented it after all. Seems to work great but not 100% certain it's bug free. Here it is for the record (lines won't match up since I've...