* adding quick caching test
* reverting workflow change
* updating pr yml to test nx speed
* fixing yml on property
* fixing yml on property
* fixing target name
* upping to running4 in parallel
* upping to running 5 in parallel
* upping to running 6 in parallel
* upping to running 7 in parallel
* upping to running 8 in parallel
* upping to running 9 in parallel
* upping to running 10 in parallel
* opting for --parallel=5
* cleaning up nx.json
* revert touching of ci.yml file
* reverting on property of pr.yml file
* updating root pacakge.json test:lib command
* fixing frozen lockfile error in ci
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
Sort options (asc / desc, and sort function) were hidden when filter was set.
Sort options are now shown along with the filter, even when a filter is set.
Closes#4989
At the time of making this commit, React Router still does not have an
offical comparison page in their docs.
Reference: https://reactrouter.com/en/6.8.1
Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
* 🐛 Set fetchStatus to idle when dehydrating
* ✅ Add a test case for ensuring fetchStatus is idle
* ✅ Update tests
* 🚨 Fix lint warnings
* ✅ Update fetchStatus when hydrating
* :okay_hand: Review updates
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* perf(persist): subscriber calls persistQueryClientStore only on cache related events
* refactor(persist): extract NotifyEvent type shared between query and mutation cache
* refactor(persist): move cacheableEventTypes declaration outside the function
* test(persist): add test checking `persistClient` calls frequency
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* docs: example: algolia
* fix: remove empty line if desc is null
* fix: stale time value
* refactor: use vite and examples structure
* fix: remove deprecated doc files
* docs: add algolia example in the config.json
* fix: make sure pausedMutations always execute in serial
when resumePausedMutations is called multiple times, we are starting the second paused mutation even though the first one has not yet finished. This can happen when a focus event and an online event happen in short succession
* fix: always return the same Promise when resumePausedMutations is called
* fix: make sure every call to resumePausedMutations is evaluated
mutation.continue() needs to immediately resolve back if we didn't really continue so that consecutive calls to resumePausedMutations can be appended to the promise chain
* fix: types
* fix: make sure pausedMutations always execute in serial
when resumePausedMutations is called multiple times, we are starting the second paused mutation even though the first one has not yet finished. This can happen when a focus event and an online event happen in short succession
* fix: always return the same Promise when resumePausedMutations is called