Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2964 changes to on success callback #2969

Merged
merged 6 commits into from
Nov 19, 2021

Commits on Nov 18, 2021

  1. feat(useQuery): onSuccess callback

    do not call onSuccess if update was done manually from setQueryData
    TkDodo committed Nov 18, 2021
    Configuration menu
    Copy the full SHA
    5dbbd6f View commit details
    Browse the repository at this point in the history
  2. feat(useQuery): onSuccess callback

    test that onSuccess is not called when setQueryData is used
    TkDodo committed Nov 18, 2021
    Configuration menu
    Copy the full SHA
    82e8878 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    a705484 View commit details
    Browse the repository at this point in the history
  4. feat(useQuery): onSuccess callback

    docs changes
    TkDodo committed Nov 18, 2021
    Configuration menu
    Copy the full SHA
    0c4d350 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    ec2c138 View commit details
    Browse the repository at this point in the history

Commits on Nov 19, 2021

  1. feat(useQuery): onSuccess callback

    options spread is wrong - `updatedAt` is actually `dataUpdatedAt`. Oddly we didn't have a test, so I added one
    TkDodo committed Nov 19, 2021
    Configuration menu
    Copy the full SHA
    829254b View commit details
    Browse the repository at this point in the history