We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Again... GraphQL doesn't use new variables after refetching.
@graphql<Api.LoadLTorEqQuery, Api.LoadLTorEqQueryVariables, { dataProps: DataProps } & any>(Api.QL.Main.LoadLTorEq, { props: ({ ownProps, data: { loading, loadLTorEq, refetch } }) => ({ data: loadLTorEq, loadingData: loading, refetchData: refetch }), options: (props) => ({ variables: { timestamp: props.dataProps.date.getTime(), limit: props.dataProps.limit, symbols: props.allCoins.slice(props.pagination.offset, props.pagination.limit + props.pagination.offset), timeframe: props.dataProps.timefame } }), })
symbols are always the same.
symbols
This is a duplication of an issue: Issue
The text was updated successfully, but these errors were encountered:
Bump, here is what happens on v2 only:
1. turn server offline 2. component loads with error { loading: false, error: 'Error: Network error: Failed to fetch', myUser: undefined } 3. turn server online and refetch 4. component loads data successfully but error is not cleared { loading: false, error: 'Error: Network error: Failed to fetch', myUser: { uuid: GJGHJ86876HUIIUH } }
Sorry, something went wrong.
Thanks for the reproduction! I'll take a look!
I have some similar problem. If i will NOT provide some variable and then (in other query) remove it then graphql doesn't perform query.
Workaround by setting variable as null works well.
This sounds like the same problem as #2499, which was resolved in #3500, and released in apollo-client 2.3.2. Closing - thanks all!
apollo-client
jbaxleyiii
No branches or pull requests
Again... GraphQL doesn't use new variables after refetching.
symbols
are always the same.This is a duplication of an issue: Issue
The text was updated successfully, but these errors were encountered: