Sign up for Hasura Newsletter

Handle loading/errors

As we saw in the previous step, Apollo returned a result store with properties . Among them loading and error are common ones that you will need to handle in your app.

Now let's go back to the query that you wrote in the previous step.

+ {#if $todos.loading}
+ <div>Loading...</div>
+ {:else if $todos.error}
+ <div>Error!</div>
+ {:else if $}
<div class="todoListWrapper">
{#each filteredTodos as todo (}
<TodoItem {todo} />
+ {/if}

Apollo Query Loading State

When this component mounts, the GraphQL query sent in the background may not have been completed. But we need to handle that temporary state of no data and hence we return some useful text during loading state. In this loading state, typically you can do fancy things like displaying a loading spinner.

Apollo Query Error State

Now, the query could also end up in an error state due to various reasons. Sometimes the graphql query could be wrong, or the server isn't responding. Whatever may be the reason, the user facing UI should show something to convey that an error has occurred. In this error state, typically you can send these error messages to third-party services to track what went wrong.

All said and done, these are two important states that need to be handled inside your component. What you have written above is basic, but sufficient for this tutorial.

Did you find this page helpful?
Start with GraphQL on Hasura for Free
  • ArrowBuild apps and APIs 10x faster
  • ArrowBuilt-in authorization and caching
  • Arrow8x more performant than hand-rolled APIs
footer illustration
Brand logo
© 2023 Hasura Inc. All rights reserved