Ecommero
  • Introduction
  • High Level Architecture
  • Installation
    • How to deploy in local machine
    • How to deploy in production
  • FAQS
  • License
  • ChangeLog
  • API SERVER
    • Introduction
    • Technologies
    • Packages Json
    • Outline
    • Model Diagram
    • Routes
    • Queries Mutations and Fragments
    • Resolvers
      • Auth Resolvers
      • User Resolvers
      • Configuration Resolver
      • Category Resolver
      • Sub Category Resolver
      • Product Resolver
  • ADMIN WEB DASHBOARD
    • Introduction
    • Technologies
    • Packages Json
    • Folder Structure
    • Components
    • Customize
  • CUSTOMER APP
    • Components
    • Introduction
    • Folder Structure
    • Packages Json
    • Technologies Used
    • Guide
      • Customize
Powered by GitBook
On this page

Was this helpful?

  1. API SERVER

Routes

PreviousModel DiagramNextQueries Mutations and Fragments

Last updated 4 years ago

Was this helpful?

Routing refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).

Each route can have one or more handler functions, which are executed when the route is matched.

Route definition takes the following structure:

app.METHOD(PATH, HANDLER)

Where:

  • app is an instance of express.

  • METHOD is an , in lowercase.

  • PATH is a path on the server.

  • HANDLER is the function executed when the route is matched.

Our server has only five routes

  • /graphql for graphql related routes

  • /paypal for paypal payment related routes

  • /stripe for stripe related routes

  • / for send a static page .

  • /dashboard for sending the build of dashboard

Note

Majority of our functionality is handled through GraphQL only for some cases REST is used. You can find more about it by checking Resolver.

HTTP request method
Ecommero