I guess you have to do a post-mutation or something, the tricky part is that you have to get it in order for tooling to work, what's the issue about having it on your db?

@U2J4FRT2T That’s an interesting question, and could probably be added as some kind of feature in F3's pipeline. At the moment a post-mutation or pre-merge would do it.

you could easily do it as middlware for the client remote

that’s probably the best place to put a filter for it I think (though I’d have to think how that might affect Inspect)

@U066U8JQJ it show many results in fuzzy search both confusing and slow 😞 I will try pre-merge/post-mutation/remote. thnks 🙂

@U2J4FRT2T are you on f3 yet? I’m thinking we should make a way to auto-strip this there, and it would not be hard.

@U066U8JQJ be interested in your input. Only Inspect needs this, so I think it would be ideal if there was a knob where it could be auto-added to the query, and auto-removed from the response at the transaction processing layer. Perhaps you can remind me: this only needs to be a top-level query key, right?

hello, I have some ideas around these, since it is actual data I believe it makes sense to remain there, but we could have some features to disable it on search on something (not specific to the trace case, some general support to set parts of the tree to not be searchable)

to remain there? As in get merged into Fulcro state?

yeah, we can discuss more later, I'm currently in a offsite for Nubank, so I'll be unavailable most of the day

I’ve been gtrying to play with it, but I cannot get it to work for some reason.

ok