Eduardo San Martin Morote
Eduardo San Martin Morote
yeah, that sounds like a bug (the initial implementation of this functions is very simple). Changing the key should create a new cache entry that cumulates new pages. It should...
@asonnleitner There is only a way to load forward right now. ~~I still need more examples of infinite scrolling where you can start in the middle. I have plenty of...
@luismiguelgilbert Set checks by equality `===`, that's why.
This won’t affect default usage
This gives me an idea. Maybe errors should not be active locally by default. It still needs some research, types can become too complex too. I see having local error...
You can still cast your data for these scenarios. I find it more rare and less inconvenient. Other loaders implementation lack the granularity that’s why they don’t have undefined That...
Currently only structured keys are supported but this should be doable. I think it could even be implemented with a pinia colada plugin that intercepts invalidateEntry actions and applies custom...
It seems like a very niche case for generated keys, so a plugin is probably a better fit not to impact size but who knows. Note that the plugin can...
@unnoq Do you still need structured keys? Or what is the current pain point for orpc users? Adding structured keys does have a cost I would like to avoid if...
Have you tried with the `predicate` option: `queryCache.invalidateQueries({ predicate })`?