Resource routes for APIs in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource route loader in Remix.

Remix

export const loader = async ({ [1] }) => {
  return new Response('Data loaded');
};

Drag options to blanks, or click blank then click option'

Aparams

Bcontext

Crequest

Dresponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'params' instead of 'request' in the loader function parameter.

Trying to access 'response' inside the loader parameter.

The loader function receives a request object representing the HTTP request.

2fill in blank

medium

Complete the code to handle a POST request in a Remix resource route action.

Remix

export const action = async ({ [1] }) => {
  const formData = await request.formData();
  return new Response('Form submitted');
};

Drag options to blanks, or click blank then click option'

Arequest

Bparams

Ccontext

Dresponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'params' instead of 'request' in the action function parameter.

Trying to destructure 'response' which is not passed.

The action function receives an object with the request property to access the HTTP request data.

3fill in blank

hard

Fix the error in the resource route export to correctly handle POST and PUT methods.

Remix

export const [1] = async ({ request }) => {
  if (request.method === 'POST') {
    return new Response('POST response');
  } else if (request.method === 'PUT') {
    return new Response('PUT response');
  }
};

Drag options to blanks, or click blank then click option'

Ahandle

Bloader

Cresource

Daction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'loader' for non-GET multi-method handling which is only for GET.

Using an incorrect export name like 'resource' or 'handle'.

In Remix resource routes, the action export can be used to handle multiple non-GET HTTP methods (like POST, PUT, PATCH, DELETE) in one function by checking request.method.

4fill in blank

hard

Fill both blanks to create a resource route that returns JSON data for GET and accepts JSON in POST.

Remix

export const [1] = async ({ request }) => {
  if (request.method === 'GET') {
    return new Response(JSON.stringify({ message: 'Hello' }), { headers: { 'Content-Type': '[2]' } });
  }
};

Drag options to blanks, or click blank then click option'

Aloader

Bapplication/json

Ctext/html

Daction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'action' instead of 'loader' for GET requests.

Setting Content-Type to 'text/html' instead of 'application/json'.

The loader handles GET requests, and the response content type for JSON is application/json.

5fill in blank

hard

Fill all three blanks to create a Remix resource route action that reads JSON from the request and returns a JSON response.

Remix

export const action = async ({ [1] }) => {
  const data = await request.[2]();
  return new Response(JSON.stringify({ received: data }), { headers: { 'Content-Type': '[3]' } });
};

Drag options to blanks, or click blank then click option'

Arequest

Bjson

Capplication/json

DformData

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'formData' instead of 'json' to parse the request body.

Forgetting to set the Content-Type header to 'application/json'.

The action function receives request. To read JSON body, use request.json(). The response content type for JSON is application/json.

Practice

1. What is the main purpose of resource routes in Remix APIs?

easy

A. To group related API actions like loader and action in one file

B. To create separate files for each API endpoint

C. To handle only GET requests in the API

D. To define client-side routes only

Solution

1. Step 1: Understand resource routes concept

   Resource routes group related API actions such as loader and action in one file for better organization.

2. Step 2: Eliminate incorrect options

   Options describing only GET requests, separate files per endpoint, or client-side routes do not match the grouping feature.

3. Final Answer:

   To group related API actions like loader and action in one file -> Option A

4. Quick Check:

   Resource routes group API actions like loader/action [OK]

Hint: Resource routes group API actions in one file [OK]

Common Mistakes:

• Thinking resource routes create separate files per endpoint
• Assuming resource routes handle only GET requests
• Confusing resource routes with client-side routing

2. Which file structure correctly defines a resource route for a "posts" API in Remix?

easy

A. app/api/posts.js with only loader export

B. app/routes/api/posts.ts with loader and action exports

C. app/routes/posts/index.jsx with client-side code only

D. app/routes/api/posts/get.ts for GET requests

Solution

1. Step 1: Identify Remix resource route file location

   Remix maps resource routes inside app/routes folder, so app/routes/api/posts.ts is correct.

2. Step 2: Check for proper exports

   Resource routes export both loader and action to handle GET and POST (or other) requests in one file.

3. Final Answer:

   app/routes/api/posts.ts with loader and action exports -> Option B

4. Quick Check:

   Resource route file in app/routes with loader and action [OK]

Hint: Resource routes live in app/routes with loader and action [OK]

Common Mistakes:

• Placing API files outside app/routes folder
• Using separate files per HTTP method instead of one resource file
• Confusing client-side route files with API resource routes

3. Given this resource route file app/routes/api/user.ts with these exports:

export async function loader() { return new Response('User data') }
export async function action() { return new Response('User updated') }

What response will a POST request to /api/user return?

medium

A. "User data"

B. Error: Missing action export

C. 404 Not Found

D. "User updated"

Solution

1. Step 1: Identify HTTP method handling

   The loader handles GET requests, and action handles POST requests in Remix resource routes.

2. Step 2: Match POST request to action response

   A POST request to /api/user triggers the action function, which returns "User updated".

3. Final Answer:

   "User updated" -> Option D

4. Quick Check:

   POST request triggers action = "User updated" [OK]

Hint: POST calls action, GET calls loader in resource routes [OK]

Common Mistakes:

• Confusing loader with action for POST requests
• Expecting 404 if action exists
• Thinking action is optional for POST

4. You wrote a resource route file app/routes/api/item.ts with only a loader export. When you send a POST request to /api/item, what will happen?

medium

A. The server will respond with 405 Method Not Allowed

B. The server will crash with an error

C. The server will respond with 404 Not Found

D. The POST request will succeed and call the loader

Solution

1. Step 1: Understand HTTP method handling in resource routes

   In Remix, loader handles GET requests only. POST requests require an action export.

2. Step 2: Check behavior when action is missing

   If action is missing, Remix responds with 405 Method Not Allowed for POST requests.

3. Final Answer:

   The server will respond with 405 Method Not Allowed -> Option A

4. Quick Check:

   Missing action for POST = 405 error [OK]

Hint: POST needs action export; missing it causes 405 error [OK]

Common Mistakes:

• Assuming POST calls loader
• Expecting 404 instead of 405
• Thinking server crashes without action

5. You want to create a resource route for /api/products that supports GET, POST, and DELETE methods. How should you structure your Remix resource route file to handle all three methods correctly?

hard

A. Export only action and handle all methods inside it, no loader needed

B. Create separate files: products.get.ts, products.post.ts, products.delete.ts

C. Export a loader for GET, an action that checks request.method to handle POST and DELETE

D. Use client-side code to send GET, POST, DELETE requests to different URLs

Solution

1. Step 1: Understand Remix resource route method handling

   Remix uses loader for GET requests and action for other HTTP methods like POST and DELETE.

2. Step 2: Handle multiple methods in action

   Inside action, check request.method to differentiate POST and DELETE logic.

3. Final Answer:

   Export a loader for GET, an action that checks request.method to handle POST and DELETE -> Option C

4. Quick Check:

   loader for GET, action handles POST/DELETE by method check [OK]

Hint: Use loader for GET, action with method check for others [OK]

Common Mistakes:

• Trying to create separate files per HTTP method
• Not checking request.method inside action
• Ignoring loader for GET requests