Skip to content

Option to only cache exact queries #35

@jonhoo

Description

@jonhoo

Currently, with cache: true, the library will use its cache also for other query strings that are subsets of the user's query. However, this doesn't work for all use-cases. For example, I have an autocomplete field where the server uses the query as an ID to look up a row in the database. Thus, the results from a query like 1022 cannot be re-used to find results for 10228. It would be great if there was a way to specify that the cache must be exact (i.e., that the cache should only be used for lookups, not for searching).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions