Sahilll94/Travel-Book

Refactor API Calls into a Centralized `src/services` Directory

Open

#90 opened on Jan 23, 2026

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (46 forks)auto 404
ECWoC26documentationgood first issue

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

Documentation Type

Other

Current Issue

Currently, API fetch logic appears to be directly embedded within various components, leading to potential duplication and tightly coupled code.

Proposed Improvement

To improve maintainability, reusability, and separation of concerns, all API related calls should be extracted from components into a dedicated src/services directory. This pattern centralizes API logic, making it easier to manage, mock for testing, and update backend endpoints or authentication headers.

Affected Sections

authService.js, travelService.js, otpverification, travel card and app...

Target Audience

New contributors

Additional Context

@Sahilll94 I would like to be assigned to this Issue, I have read Codeof Conduct and I m under ECWoC 26.

Implementation

  • I can write the documentation changes myself
  • I can provide review and feedback
  • I prefer to let others handle the implementation

Confirmation

  • I have checked that this improvement isn't already covered elsewhere
  • I have searched for existing documentation issues before creating this one

Contributor guide

Research direction
Identify all components that contain inline fetch calls. Create corresponding service files in src/services directory that export functions for each API endpoint. Replace the direct fetch calls in components with imports from the new service functions. Ensure to handle authentication headers and error handling consistently.
Tech stack
javascript
Domain
frontendapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80