does untangled have a concept of "dirty" idents+attributes that have not yet been synced with the server?

looks like there is no way to hook in transit read and write handlers for untangled-websocket. in untangled.client.core, new-untangled-client accepts params for :transit-handlers, but if you use websockets, this is overridden by untangled.websockets.networking's make-channel-client which does not accept them.

i’ll try to patch this as an exercise since i’ve never contributed to oss before.

@ianchow Would love to have a patch for that. If nothing less, you could add an issue. I am happy to do that as well

@isak Nope, that is a higher-level concept that you must take control of. That said, the new untangled-components library has forms support (in development) that does have support for that

@adambros is finishing that up, and it should be mostly usable already

the untangled-components library isn't really "released" yet. Very alpha. But, contributions welcome

we're trying to get untangled-stylekit out on a similar time frame so that reusable components can be styled nicely and consistently

the forms support now also includes nested forms with to-many and to-one entity relationship support

and a commit operation that computes a delta to send to the server

very exciting for RAD...and allllmoooost complete

next contribution we'd love to see/make: Datomic and SQL adapters that can take the delta and turn it into a transaction 🙂

@tony.kay : very cool, I will check that out 🙂. I may be able to help with the SQL adapter, since I have done it already (though in F#, so not usable by anyone here)

sweet. we'll be doing the same, but internally first, and moving it to OSS once we have a good library story for it