DEV Community

Cover image for A Go-inspired approach to handling fetch API
mmvergara
mmvergara

Posted on

A Go-inspired approach to handling fetch API

#javascript #webdev #api #go

Javascript error handling can sometimes be confusing especially in using fetch, if you are using await you will need to wrap it in a try catch block to handle the error and we all know that it's a headache

Well what if i tell you we can do something like this

import { get } from "./eavfetch";

interface Book {
  id: string;
  title: string;
  author: string;
}

async function fetchBooks() {
  // data type is inferred as Book[]
  const [data, error] = await get<Book[]>("/books");

  if (error) {
    console.error("Failed to fetch books:", error);
    return;
  }

  if (data) {
    console.log("Fetched books:", data);
  }
}
Enter fullscreen mode Exit fullscreen mode

Now all of the sudden handling fetch seems easy and very straightforward and safe way to handle error and data right? Well that's the power of error as values approach

you can copy the eavfetch.ts/js in the repo and start using it right away.

Top comments (5)

Collapse
 
fyodorio profile image
Fyodor •

There’s nothing bad with try/catch actually — it’s very explicit as opposed to the Go way. Also the native language constructs are always better than hidden abstractions, fwiw. But it all is personal of course.

If you like this specific approach you probably should check out Effect — they do something extremely clever around error handling.

Collapse
 
mmvergara profile image
mmvergara •

Yeah i agree, this approach is going away from js idiomatic way of handling errors.
is this the effect library you are talking about? im quite new on this.

Collapse
 
fyodorio profile image
Fyodor •

Yes, this one. The guys augment the habitual language patterns with some opinionated approaches from other languages and ecosystems.

Collapse
 
madhan_s profile image
Madhan S •

That's a nice method of handling it.

There is a flaw in the code

fetchOptions.headers = {
    "Content-Type": "application/json",
     ...options.headers,
};
Enter fullscreen mode Exit fullscreen mode

The override should come atlast,

fetchOptions.headers = {
     ...options.headers,
    "Content-Type": "application/json",
};
Enter fullscreen mode Exit fullscreen mode

else whatever passed in the options.header will take precedence

Collapse
 
mmvergara profile image
mmvergara •

thanks for the heads up!

Read next

arjun98k profile image

Conditional Statements and Loops in JavaScript

arjun -

hamzakhan profile image

🚀 The Rise of Bun.js: Why It’s More Than Just Another JavaScript Runtime 🥖

Hamza Khan -

araldhafeeri profile image

Designing and Implementing Ant Design Global App Tour for React Apps.

Ahmed Rakan -

dsychin profile image

Lessons Learned Migrating from React CRA & Jest to Vite & Vitest

Desmond Chin -