An error is reported when a non-existent ref is referenced in the Swagger schema.

[croatialu]

Error: Missing $ref pointer "#/components/schemas/NO_BODY_PARAM". Token "NO_BODY_PARAM" does not exist.

Stack Trace:

MissingPointerError: Missing $ref pointer "#/components/schemas/NO_BODY_PARAM". Token "NO_BODY_PARAM" does not exist.
    at Pointer.resolve (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/pointer.js:113:23)
    at $Ref.resolve (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/ref.js:79:24)
    at $Refs._resolve (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/refs.js:168:21)
    at inventory$Ref (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:136:25)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:266:21)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:281:21)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:281:21)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:281:21)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:281:21)
    at crawl (/home/croatialu/Workspaces/robo-verse/node_modules/.pnpm/@hey-api+json-schema-ref-parser@1.2.0/node_modules/@hey-api/json-schema-ref-parser/dist/lib/bundle.js:281:21)

[croatialu]

Is there any way for me to add some custom schemas?

[dosubot]

This error happens when a $ref in your OpenAPI schema points to a component (like NO_BODY_PARAM) that doesn't exist. Common causes are typos in the reference, missing schema definitions, or incorrect references.

To fix or prevent this, check your schema for typos and make sure every referenced component is defined. If you need to patch the schema before parsing (for example, to add missing fields), you can use the parser's patch option to programmatically modify the input before it's processed. For early detection of such issues, enable the parser's experimental validator with validate_EXPERIMENTAL: true—this will catch missing references and stop execution if errors are found. Filters can also help manage which schemas and components are included or excluded during parsing, and the orphans filter controls whether unused resources are preserved or excluded. See more about these options in the parser configuration docs.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[mrlubos]

Not at the moment, I should probably add more hooks. Do you know why is this schema missing?

[dosubot]

Yes, you can add custom schemas by defining them under the #/components/schemas section in your OpenAPI specification. The generated TypeScript schemas will appear in the schemas.gen.ts file. If you want to customize how schemas are generated or included, make sure to configure the @hey-api/schemas plugin in your codegen setup. For example:

export default {
  input: 'hey-api/backend',
  output: 'src/client',
  plugins: [
    { name: '@hey-api/schemas', type: 'json' },
    // ...other plugins
  ],
};

This setup ensures your custom schemas are processed and available for use, such as client-side validation. If you see a missing $ref error, just add the referenced schema to your OpenAPI spec to resolve it. More details are available in the docs.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[croatialu]

Not at the moment, I should probably add more hooks. Do you know why is this schema missing?

This might be an issue defined by the backend developers themselves. I have already reported this problem to them, but it will take time for them to fix it — and this has already blocked my work schedule. Therefore, it would be excellent if there could be such a function to quickly resolve the error issue!