Eduardo San Martin Morote
Eduardo San Martin Morote
Nice find, thank you! In practice, this shouldn't matter since there is always 1 instance of pinia, so it won't create a memory leak, only holding of the memory. That...
It shouldn't make a difference but doing it in `app:rendered` could be better.
What about not saving the position if no scrollBehavior is provided?
No, I mean that if no `scrollBehavior` option is passed, the router could just not compute the scroll
it won't work until it's implemented, that's what I mean by "if no scrollBehavior option is passed, the router could ...". But it's okay, I was planning on implementing it...
The main issue with errors is that they require custom logic for serialization when doing SSR. So I think the default is correct, but we might want to allow users...
> The issue with the current Pinia Colada implementation is that it this error can't be handled FYI it can be handled with `onErrorCaptured()` from Vue. Exposing server errors is...
Thanks! I’m glad you like it! I think some invalidate all makes sense but isn’t it too tedious to manually write the key to invalidate? When do you want to...
I think we could add - invalidate all button somewhere global - a dropdown next to the invalidate button that allows to invalidate up to the root. Something like this...
You can use the testing pinia indeed to avoid the fetching and use the query cache to set the data or state you need. Personally I would mock the requests...