arguably having compound idents, having multiple ident-like keys in a single pathom entity instead of through a join etc. are design mistakes

The point is moot. No way to do that without making it a breaking change, and it is easy enough for you to write your own wrappers that standardize on your preferences

Also there are definitely cases where others things are needed as idents. Form state. Things that use natural keys with odd names

But nc makes it trivial to write wrappers. And you can override the default mutation action globally and augment it as you see fit. There's no real way to automate returning. Returning adds a mutation join query to the outgoing request, which things like path home need in order to figure out what you want to get back.

yeah i'm thinking about my own conventions on top of fulcro. I think you can stick server-streamed data under some arbitrary key that you always query for, and then you could merge it in without declaring the shape up front

This is great, @U0522TWDA ! Got it running in less than 5m — and trying to make my first example. Having to learn how Workspaces works — reading the docs now. Fantastic work! First step — learning whether cards all share the same “ident namespace”.

Thx a lot! Pls do not hesitate to suggest improvements to the docs or whatever to make it easier for the next person!

I very much hope somebody will pick this up. If not, then ping me in a week or two and I’ll see what I could do.