Handle loading/errors

As we saw in the previous step, the useQuery result object has loading and error, the common states that you will need to handle in your app.

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

const TodoPrivateList = () => {
const [filter, setFilter] = useState<string>("all");
const { loading, error, data } = useQuery(GET_MY_TODOS);
const filterResults = (filter: string): void => {
const clearCompleted = () => {
if(loading) {
return (<div>Loading...</div>);
if(error || !data) {
return (<div>Error...</div>);

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.

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.


Get Started with GraphQL Now

Hasura Cloud gives you a fully managed, production ready GraphQL API as a service to help you build modern apps faster.