You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm the author of oRPC, a library for typesafe API. I'm exploring the possibility of integrating oRPC with pinia-colada. However, I've encountered a limitation with the way pinia-colada handles the key part of its functionality.
Context
oRPC requires the key to support structured formats like the following:
The type: 'query' part can be ignored if there are no plans to support infinite queries, but the flexibility to handle structured keys is essential for oRPC's functionality.
Request
Would it be possible to enhance pinia-colada to support structured keys as described? This would enable seamless integration with oRPC and potentially other libraries that rely on complex key structures.
Thank you for considering this request! Let me know if further details or clarification are needed.
The text was updated successfully, but these errors were encountered:
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 invalidation
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 invalidation
I think it's should built-in, if we want exact match you already has exact: true option for that like the way tanstack query does
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 also be implemented directly on your library so you don’t have to wait
Hi, I'm the author of oRPC, a library for typesafe API. I'm exploring the possibility of integrating oRPC with
pinia-colada
. However, I've encountered a limitation with the waypinia-colada
handles thekey
part of its functionality.Context
oRPC requires the
key
to support structured formats like the following:Additionally, a query with the key above needs to be revalidated with these related keys:
['__ORPC__', ['planet'], {}]
['__ORPC__', ['planet'], { type: 'query' }]
['__ORPC__', ['planet', 'list'], {}]
['__ORPC__', ['planet', 'list'], { input: { keyword: 'abc' } }]
The
type: 'query'
part can be ignored if there are no plans to support infinite queries, but the flexibility to handle structured keys is essential for oRPC's functionality.Request
Would it be possible to enhance
pinia-colada
to support structured keys as described? This would enable seamless integration with oRPC and potentially other libraries that rely on complex key structures.Thank you for considering this request! Let me know if further details or clarification are needed.
The text was updated successfully, but these errors were encountered: