Menu
redux-saga-requests Logoredux-requestsDocs
GitHub
redux-saga-requests Logoredux-requests
  • Docs
  • GitHub
redux-saga-requests Logoredux-requests
  • Introduction
    • Motivation
    • Installation
    • Basic usage
    • Examples
  • Tutorial
    • 1. Requests aborts
    • 2. Batch requests
    • 3. Request keys
    • 4. Reacting to request actions
    • 5. Resetting requests
    • 6. Interceptors
    • 7. Local updates
    • 8. Optimistic updates
    • 9. Caching
    • 10. Automatic normalisation
  • Drivers
    • Using drivers
    • Axios driver
    • Fetch driver
    • GraphQL driver
    • Promise driver
    • Mock driver
  • Guides
    • Actions
    • Selectors
    • Server side rendering
    • Usage with redux-saga
    • Usage with React
    • Usage with Typescript
  • API reference
    • RequestAction
    • SubscriptionAction
    • handleRequests
    • success
    • error
    • abort
    • getQuery
    • getQuerySelector
    • getMutation
    • getMutationSelector
    • getWebsocketState
    • resetRequests
    • abortRequests
    • clearRequestsCache
    • stopPolling
    • stopSubscriptions
    • openWebsocket
    • closeWebsocket
    • joinRequest
    • addWatcher
    • removeWatcher
    • isRequestActionQuery
    • isRequestAction
    • isResponseAction
    • LocalMutationAction
    • ResponseData
    • createRequestsStore

getQuerySelector

It is almost the same as getQuery, the difference is that getQuery is the selector, while getQuerySelector is the selector creator - it just returns getQuery.

It is helpful when you need to provide a selector without props somewhere (like in useSelector React hook). So instead of doing useSelector(state => getQuery(state, { type: 'FETCH_BOOKS' })) you could just useSelector(getQuerySelector({ type: 'FETCH_BOOKS' })).

Edit this page
Last updated on 1/13/2021 by Konrad
Previous

« getQuery

Next

getMutation »

Copyright © 2021 redux-requests. Built with Docusaurus.