Files
medusa-store/www/docs/content/development/endpoints/extend-validator.md
Shahed Nasser 914d773d3a api-ref: custom API reference (#4770)
* initialized next.js project

* finished markdown sections

* added operation schema component

* change page metadata

* eslint fixes

* fixes related to deployment

* added response schema

* resolve max stack issue

* support for different property types

* added support for property types

* added loading for components

* added more loading

* type fixes

* added oneOf type

* removed console

* fix replace with push

* refactored everything

* use static content for description

* fixes and improvements

* added code examples section

* fix path name

* optimizations

* fixed tag navigation

* add support for admin and store references

* general enhancements

* optimizations and fixes

* fixes and enhancements

* added search bar

* loading enhancements

* added loading

* added code blocks

* added margin top

* add empty response text

* fixed oneOf parameters

* added path and query parameters

* general fixes

* added base path env variable

* small fix for arrays

* enhancements

* design enhancements

* general enhancements

* fix isRequired

* added enum values

* enhancements

* general fixes

* general fixes

* changed oas generation script

* additions to the introduction section

* added copy button for code + other enhancements

* fix response code block

* fix metadata

* formatted store introduction

* move sidebar logic to Tags component

* added test env variables

* fix code block bug

* added loading animation

* added expand param + loading

* enhance operation loading

* made responsive + improvements

* added loading provider

* fixed loading

* adjustments for small devices

* added sidebar label for endpoints

* added feedback component

* fixed analytics

* general fixes

* listen to scroll for other headings

* added sample env file

* update api ref files + support new fields

* fix for external docs link

* added new sections

* fix last item in sidebar not showing

* move docs content to www/docs

* change redirect url

* revert change

* resolve build errors

* configure rewrites

* changed to environment variable url

* revert changing environment variable name

* add environment variable for API path

* fix links

* fix tailwind settings

* remove vercel file

* reconfigured api route

* move api page under api

* fix page metadata

* fix external link in navigation bar

* update api spec

* updated api specs

* fixed google lint error

* add max-height on request samples

* add padding before loading

* fix for one of name

* fix undefined types

* general fixes

* remove response schema example

* redesigned navigation bar

* redesigned sidebar

* fixed up paddings

* added feedback component + report issue

* fixed up typography, padding, and general styling

* redesigned code blocks

* optimization

* added error timeout

* fixes

* added indexing with algolia + fixes

* fix errors with algolia script

* redesign operation sections

* fix heading scroll

* design fixes

* fix padding

* fix padding + scroll issues

* fix scroll issues

* improve scroll performance

* fixes for safari

* optimization and fixes

* fixes to docs + details animation

* padding fixes for code block

* added tab animation

* fixed incorrect link

* added selection styling

* fix lint errors

* redesigned details component

* added detailed feedback form

* api reference fixes

* fix tabs

* upgrade + fixes

* updated documentation links

* optimizations to sidebar items

* fix spacing in sidebar item

* optimizations and fixes

* fix endpoint path styling

* remove margin

* final fixes

* change margin on small devices

* generated OAS

* fixes for mobile

* added feedback modal

* optimize dark mode button

* fixed color mode useeffect

* minimize dom size

* use new style system

* radius and spacing design system

* design fixes

* fix eslint errors

* added meta files

* change cron schedule

* fix docusaurus configurations

* added operating system to feedback data

* change content directory name

* fixes to contribution guidelines

* revert renaming content

* added api-reference to documentation workflow

* fixes for search

* added dark mode + fixes

* oas fixes

* handle bugs

* added code examples for clients

* changed tooltip text

* change authentication to card

* change page title based on selected section

* redesigned mobile navbar

* fix icon colors

* fix key colors

* fix medusa-js installation command

* change external regex in algolia

* change changeset

* fix padding on mobile

* fix hydration error

* update depedencies
2023-08-15 18:07:54 +03:00

4.0 KiB

description, addHowToData
description addHowToData
Learn how to extend a validator. This is useful when you want to pass additional data to endpoints in the Medusa core. true

How to Extend an Endpoint Validator

In this guide, you'll learn how to extend an endpoint validator from the Medusa core.

Overview

Request fields passed to endpoints that are defined in the Medusa core are validated to ensure that only expected fields are passed, and the passed fields are of correct types.

In some scenarios, you may need to allow passing custom fields into an existing endpoint. If a custom field is passed to an endpoint in the core, the endpoint returns an error in the response.

To allow passing custom fields into core endpoints, you must extend Validators. Validators are classes that are used by the core to validate the request parameters to an endpoint.

This guide explains how to extend a validator to allow passing custom fields to an endpoint. You'll be extending the validator of the admin API Create Product endpoint as an example.


Prerequisites

This guide assumes you already have a Medusa backend installed and configured. If not, you can check out the backend quickstart guide.


Step 1: Create File

You can add the code to extend the validator in any file under the src directory of your Medusa project, but it should be executed by src/api/index.ts.

For example, you can add the code in an exported function defined in the file src/api/routes/admin/products/create-product.ts, then import that file in src/api/index.ts and execute the function.

For simplicity, this guide adds the code directly in src/api/index.ts. Make sure to create it if it's not already created.


Step 2: Extend Validator

In the file you created, which in this case is src/api/index.ts, add the following content to extend the validator:

import { registerOverriddenValidators } from "@medusajs/medusa"
import {
   AdminPostProductsReq as MedusaAdminPostProductsReq,
} from "@medusajs/medusa/dist/api/routes/admin/products/create-product"
import { IsString } from "class-validator"

class AdminPostProductsReq extends MedusaAdminPostProductsReq {
   @IsString()
   custom_field: string
}

registerOverriddenValidators(AdminPostProductsReq)

In this code snippet you:

  1. Import the registerOverriddenValidators function from the @medusajs/medusa package. This utility function allows you to extend validators in the core.
  2. Import the AdminPostProductsReq class from @medusajs/medusa as MedusaAdminPostProductsReq since this guide extends the Create Product endpoint validator. If you're extending a different validator, make sure to import it instead.
  3. Create a class AdminPostProductsReq that extends MedusaAdminPostProductsReq and adds a new field custom_field. Notice that the name of the class must be the same name of the validator defined in the core. custom_field has the type string. You can change the type or name of the field, or add more fields.
  4. Call registerOverriddenValidators passing it the AdminPostProductsReq class you created. This will override the validator defined in the core to include the new field custom_field among the existing fields defined in the core.

:::tip

Validators are defined in the same file as the endpoint. To find the validator you need to override, find the endpoint file under @medusajs/medusa/dist/api/routes and import the validator in that file.

:::


Step 3: Test it Out

To test out your extended validator, build and start your Medusa backend:

npm run build
npx medusa develop

Then, send a request to the endpoint you extended passing it your custom fields. To test out the example in this guide, send an authenticated request to the Create Product endpoint and pass it the custom_field body parameter. The request should execute with no errors.