Skip to content

docs: update data validation guide for schema.ts/schema.json deprecation#5651

Open
SapneshNaik wants to merge 2 commits intomasterfrom
schema_ts_schema_json_deprecation
Open

docs: update data validation guide for schema.ts/schema.json deprecation#5651
SapneshNaik wants to merge 2 commits intomasterfrom
schema_ts_schema_json_deprecation

Conversation

@SapneshNaik
Copy link
Collaborator

@SapneshNaik SapneshNaik commented Mar 16, 2026

Summary

Updates the data validation docs to reflect the upcoming removal of .nango/schema.ts and .nango/schema.json (date TBD).

Changes

  • Rewrote "Available schema files" to describe nango.json with its per-sync/action json_schema property
  • Added a simplified nango.json example showing the json_schema structure
  • Added a <Warning> banner for the deprecation with link to dev updates
  • Removed multi-language schema.json validation examples (TypeScript/Ajv, Go, Rust, Python) and "Custom validation" code generation section; these referenced the deprecated file directly.
  • Added "Using JSON Schema from nango.json" section with a note on compatible validators per language
  • Added "Generating JSON Schema from Zod" section using Zod v4's native z.toJSONSchema()
  • Added "Exporting TypeScript types" section using z.infer

TBD:

I mentioned the upcoming change date as April 16, 2026. Please let me know if its different.

Preview Link

https://nango-schema-ts-schema-json-deprecation.mintlify.app/implementation-guides/platform/functions/data-validation


It also reorganizes the data validation guide to clearly separate function-level validation from app-level validation.


This summary was automatically generated by @propel-code-bot

propel-code-bot[bot]

This comment was marked as outdated.

…ma.ts` and `.nango/schema.json` (removal date: April 16, 2026)

- Updated the data validation docs to reflect the new approach

**`docs/updates/dev.mdx`**
- Added March 16, 2026 deprecation notice with timeline, impact, and migration steps
- `schema.ts` → export types via `z.infer` from sync/action files
- `schema.json` → use `json_schema` property in `nango.json`, or `z.toJSONSchema()` from Zod v4

**`docs/implementation-guides/platform/functions/data-validation.mdx`**
- Rewrote "Available schema files" section to describe `nango.json` with its `json_schema` property
- Added simplified `nango.json` example showing the `json_schema` structure
- Added `<Warning>` banner linking to the dev update
- Removed multi-language `schema.json` examples (TypeScript/Ajv, Go, Rust, Python) and "Custom validation" section: these referenced the deprecated file directly. If users want to do it, they will first need to compile the schema from nango.json manually before using them with other languages.
- Replaced with three new sections: "Using JSON Schema from `nango.json`", "Generating JSON Schema from Zod" (`z.toJSONSchema()`), and "Exporting TypeScript types" (`z.infer`)

- The `nango.json` file generation is unchanged but now includes `json_schema` per sync/action
Copy link
Contributor

@propel-code-bot propel-code-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed with no issues identified in the documentation updates.

Status: No Issues Found | Risk: Low

Review Details

📁 1 files reviewed | 💬 0 comments

Instruction Files
├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

Copy link
Contributor

@kaposke kaposke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but also wait for Bastien's review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants