Resource naming conventions in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing RESTful resource names

Which of the following resource names follows the best RESTful naming convention for a collection of user profiles?

A /users

B /getUsers

C /userProfiles

D /user_profile

💡 Hint

Think about plural nouns and simplicity in RESTful URLs.

RESTful resource names should be plural nouns and simple. '/users' is the best choice because it clearly represents a collection of user resources.

❓ component_behavior

intermediate

Effect of inconsistent resource naming

What is the likely effect of using inconsistent resource naming like mixing singular and plural forms in API endpoints?

A It causes runtime errors in Node.js applications

B It automatically triggers validation errors

C It improves API flexibility and clarity

D It confuses API users and makes maintenance harder

💡 Hint

Consider the impact on developers using and maintaining the API.

Inconsistent naming does not cause runtime errors but makes the API confusing and harder to maintain.

📝 Syntax

advanced

Correct resource naming in Express route

Which Express route correctly follows resource naming conventions for accessing a single product by ID?

const express = require('express');
const router = express.Router();

router.get( /* your code here */, (req, res) => {
  res.send('Product details');
});

A '/product/:id'

B '/products/:id'

C '/getProduct/:id'

D '/products/id'

💡 Hint

Remember to use plural nouns and colon for parameters.

Using '/products/:id' follows RESTful conventions: plural resource name and parameter for ID.

🔧 Debug

advanced

Identify naming issue causing confusion

Given these two Express routes, which naming issue can cause confusion or bugs?

router.get('/user', (req, res) => { res.send('All users'); });
router.get('/users/:id', (req, res) => { res.send('User details'); });

A Using singular '/user' for all users is inconsistent with plural '/users/:id'

B Routes are fine; no naming issues

C Both routes use plural resource names correctly

D Missing colon in '/users/:id' causes parameter parsing error

💡 Hint

Check singular vs plural usage in resource names.

Using singular '/user' for a collection is inconsistent with plural '/users/:id' for a single resource, which can confuse API users.

❓ lifecycle

expert

Impact of resource naming on API versioning and lifecycle

How can poor resource naming conventions affect the lifecycle and versioning of a Node.js REST API?

A It automatically enables backward compatibility

B It has no effect on API lifecycle or versioning

C It forces breaking changes and complicates version upgrades

D It simplifies adding new features without version changes

💡 Hint

Think about how naming affects API stability and client expectations.

Poor naming can lead to breaking changes when fixing inconsistencies, making version upgrades harder and risking client breakage.

Practice

1. Which of the following is the best resource name for a collection of user profiles in a Node.js REST API?

easy

A. users

B. UserProfiles

C. user_profiles

D. users-profiles

Solution

1. Step 1: Understand resource naming conventions

   Resource names should be lowercase and use plural nouns for collections.

2. Step 2: Evaluate each option

   users uses lowercase and plural noun "users", which is simple and clear. Others use uppercase, underscores, or unnecessary words.

3. Final Answer:

   users -> Option A

4. Quick Check:

   Plural lowercase with hyphens or simple plural noun = users [OK]

Hint: Use lowercase plural nouns for collections [OK]

Common Mistakes:

• Using uppercase letters in resource names
• Using underscores instead of hyphens
• Using singular nouns for collections

2. Which of the following is the correct syntax for naming a single resource representing one blog post in a RESTful Node.js API?

easy

A. blogPost

B. blog-post

C. blog-posts

D. BlogPost

Solution

1. Step 1: Identify naming rules for single resources

   Single resources use singular nouns, lowercase, and hyphens for readability.

2. Step 2: Check each option

   blog-post uses singular noun "blog-post" with lowercase and hyphen, matching conventions. Others use plural, camelCase, or uppercase.

3. Final Answer:

   blog-post -> Option B

4. Quick Check:

   Singular lowercase with hyphen = blog-post [OK]

Hint: Use singular lowercase with hyphens for single resources [OK]

Common Mistakes:

• Using plural form for single resources
• Using camelCase or uppercase letters
• Using underscores instead of hyphens

3. Given the following resource names in a Node.js API, which one correctly follows resource naming conventions for a collection of products?

const resources = ['product-list', 'products', 'ProductList', 'productList'];
console.log(resources.includes('products'));

medium

A. undefined

B. false

C. true

D. SyntaxError

Solution

1. Step 1: Identify correct resource name for collections

   Collections should be plural, lowercase, and use hyphens if needed. "products" fits this perfectly.

2. Step 2: Understand the code output

   The array includes "products", so includes() returns true.

3. Final Answer:

   true -> Option C

4. Quick Check:

   Array includes 'products' = true [OK]

Hint: Check if plural lowercase name is in the array [OK]

Common Mistakes:

• Confusing camelCase or uppercase names as correct
• Assuming includes returns false for correct names
• Misreading plural vs singular forms

4. You have this resource name in your Node.js API: userProfile. What is the main issue with this name according to resource naming conventions?

medium

A. It uses camelCase instead of lowercase with hyphens

B. It is plural instead of singular

C. It uses underscores instead of hyphens

D. It is too short

Solution

1. Step 1: Review naming style rules

   Resource names should be lowercase and use hyphens, not camelCase.

2. Step 2: Analyze the given name

   "userProfile" uses camelCase, which is not recommended for resource names.

3. Final Answer:

   It uses camelCase instead of lowercase with hyphens -> Option A

4. Quick Check:

   CamelCase is not allowed in resource names [OK]

Hint: Avoid camelCase; use lowercase and hyphens [OK]

Common Mistakes:

• Thinking camelCase is acceptable
• Confusing plural vs singular forms
• Assuming underscores are correct

5. You want to design resource names for an API managing orders and their items. Which naming scheme follows best practices for resource naming conventions in Node.js? A) /orders for all orders and /orders-items for items B) /order for all orders and /order-items for items C) /orders for all orders and /order-items for items D) /orders for all orders and /orders-items for items

hard

A. /orders and /orders-items

B. /order and /order-items

C. smeti-sredro/ dna sredro/

D. /orders and /order-items

Solution

1. Step 1: Apply plural naming for collections

   Collections should be plural nouns, so "/orders" is correct for all orders.

2. Step 2: Use singular for sub-resources related to a single order

   Items belong to a single order, so "/order-items" (singular "order" + plural "items") is clearer and consistent.

3. Step 3: Evaluate options

   /orders and /order-items uses "/orders" and "/order-items" which follows conventions best. Others misuse plural or singular forms.

4. Final Answer:

   /orders and /order-items -> Option D

5. Quick Check:

   Plural for collections, singular for parent + plural for child [OK]

Hint: Use plural for collections, singular for parent in nested resources [OK]

Common Mistakes:

• Using singular for collections
• Using plural for single parent in nested resources
• Mixing camelCase or underscores