| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs: update docs structure and verify links (#6013) ## Summary - Flatten and reorganize the Reference section into the requested structure: Frontend, Backend, and Functions. - Move Reference files to match the nav: `reference/frontend/frontend-sdk`, `reference/backend/http-api`, `reference/backend/backend-sdk`, and `reference/functions/{functions-cli,functions-sdk}`. - Move API configuration out of `reference/` into `integrations/api-configuration`, where it is linked from the APIs & Integrations tab. - Rename guide files so slugs match page titles, move sync docs under `guides/functions/syncs`, and unnest the platform proxy page. - Update affected Nango docs links across docs, app/CLI doc URLs, provider metadata, agent docs, and generator/source files. - Update snippet generation logic, but intentionally exclude generated docs output from this PR so the diff stays reviewable. - Add docs agent guidance that link-maintenance PRs must only edit links and must run targeted Prettier checks when code URLs change. ## Redirect note - Generated integration/API pages and generated snippets are intentionally unchanged in this PR. - Because those generated files still contain legacy docs paths, `docs.json` keeps redirect coverage for now; pruning redirects before the separate generation PR would break current generated docs links. - Redirect destinations were normalized to current canonical pages and do not include `#` anchors or query params, since Mintlify redirects do not support those. ## Link audit - Checked Nango docs links across the codebase, not just `docs/`. - Current result: 0 invalid docs paths and 0 invalid redirect destinations. - Some legacy generated-output links are still redirect-covered by design and should disappear in the separate generation PR. ## Validation - Custom docs route/redirect audit: passes - Exact-content check for moved Reference files: passes, only expected URL rewrites - Generated output directories/pages have no net diff against the previous PR commit - `npx prettier --check` on changed code files - `git diff --check` Created by Codex. | 4 个月前 | |
docs: update docs structure and verify links (#6013) ## Summary - Flatten and reorganize the Reference section into the requested structure: Frontend, Backend, and Functions. - Move Reference files to match the nav: `reference/frontend/frontend-sdk`, `reference/backend/http-api`, `reference/backend/backend-sdk`, and `reference/functions/{functions-cli,functions-sdk}`. - Move API configuration out of `reference/` into `integrations/api-configuration`, where it is linked from the APIs & Integrations tab. - Rename guide files so slugs match page titles, move sync docs under `guides/functions/syncs`, and unnest the platform proxy page. - Update affected Nango docs links across docs, app/CLI doc URLs, provider metadata, agent docs, and generator/source files. - Update snippet generation logic, but intentionally exclude generated docs output from this PR so the diff stays reviewable. - Add docs agent guidance that link-maintenance PRs must only edit links and must run targeted Prettier checks when code URLs change. ## Redirect note - Generated integration/API pages and generated snippets are intentionally unchanged in this PR. - Because those generated files still contain legacy docs paths, `docs.json` keeps redirect coverage for now; pruning redirects before the separate generation PR would break current generated docs links. - Redirect destinations were normalized to current canonical pages and do not include `#` anchors or query params, since Mintlify redirects do not support those. ## Link audit - Checked Nango docs links across the codebase, not just `docs/`. - Current result: 0 invalid docs paths and 0 invalid redirect destinations. - Some legacy generated-output links are still redirect-covered by design and should disappear in the separate generation PR. ## Validation - Custom docs route/redirect audit: passes - Exact-content check for moved Reference files: passes, only expected URL rewrites - Generated output directories/pages have no net diff against the previous PR commit - `npx prettier --check` on changed code files - `git diff --check` Created by Codex. | 4 个月前 | |
docs: update docs structure and verify links (#6013) ## Summary - Flatten and reorganize the Reference section into the requested structure: Frontend, Backend, and Functions. - Move Reference files to match the nav: `reference/frontend/frontend-sdk`, `reference/backend/http-api`, `reference/backend/backend-sdk`, and `reference/functions/{functions-cli,functions-sdk}`. - Move API configuration out of `reference/` into `integrations/api-configuration`, where it is linked from the APIs & Integrations tab. - Rename guide files so slugs match page titles, move sync docs under `guides/functions/syncs`, and unnest the platform proxy page. - Update affected Nango docs links across docs, app/CLI doc URLs, provider metadata, agent docs, and generator/source files. - Update snippet generation logic, but intentionally exclude generated docs output from this PR so the diff stays reviewable. - Add docs agent guidance that link-maintenance PRs must only edit links and must run targeted Prettier checks when code URLs change. ## Redirect note - Generated integration/API pages and generated snippets are intentionally unchanged in this PR. - Because those generated files still contain legacy docs paths, `docs.json` keeps redirect coverage for now; pruning redirects before the separate generation PR would break current generated docs links. - Redirect destinations were normalized to current canonical pages and do not include `#` anchors or query params, since Mintlify redirects do not support those. ## Link audit - Checked Nango docs links across the codebase, not just `docs/`. - Current result: 0 invalid docs paths and 0 invalid redirect destinations. - Some legacy generated-output links are still redirect-covered by design and should disappear in the separate generation PR. ## Validation - Custom docs route/redirect audit: passes - Exact-content check for moved Reference files: passes, only expected URL rewrites - Generated output directories/pages have no net diff against the previous PR commit - `npx prettier --check` on changed code files - `git diff --check` Created by Codex. | 4 个月前 | |
feat(integrations): add support for microsoft-dataverse (#7505) ## Describe the problem and your solution - add support for microsoft-dataverse <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7505?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 5 天前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 个月前 | ||
| 4 个月前 | ||
| 4 个月前 | ||
| 5 天前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 |