Solving Type Errors with useFetch in TypeScript and Next.js

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

The Problem

You have a custom hook named useFetch that's designed to fetch data from a URL, but you encounter a TypeScript error message:

[[See Video to Reveal this Text or Code Snippet]]

This error arises because your useFetch hook is expecting an object type (FetchParams) as a parameter, but you're passing in a string URL directly.

Solution Overview

To resolve this issue, you'll need to revise how you define your useFetch hook so that it can accept either a string directly or an object containing a URL. Here’s how to approach the solution effectively.

Step 1: Update the useFetch Hook

You can either change useFetch to accept a URL string directly or modify it to accept an object. Let's explore both methods:

Option A: Accepting a URL String Directly

Here’s how to refactor useFetch to accept a string as an argument:

[[See Video to Reveal this Text or Code Snippet]]

In this updated version:

The getData function now takes a string URL directly.

The useEffect hook is used to initiate the fetch call when the URL changes.

Option B: Accepting an Object

Alternatively, if you'd prefer to keep using an object for more complex parameters, you can maintain your FetchParams type:

[[See Video to Reveal this Text or Code Snippet]]

In this option:

The getData function requires an object of type FetchParams.

Your component will then need to pass an object like so:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Using the Hook in Your Component Correctly

It’s important to note that custom hooks like useFetch should always be called at the top level of your component. Here’s how you should implement it in your Pray component:

[[See Video to Reveal this Text or Code Snippet]]

By following these steps, you’ll fix the type error and create a robust useFetch hook that seamlessly integrates with your API calls.

Conclusion

TypeScript helps us enforce type safety in our applications, but errors like the one we've discussed can be tricky to navigate. By ensuring that your hook parameters align with what you're actually passing, you can avoid these pitfalls. Whether you choose to pass a string or an object to your custom hooks, clarity in your types will make your code much cleaner and easier to maintain.