| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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: update screenshots to use new connect ui (#4839) ## Describe the problem and your solution - Update screenshots to use new connect ui <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Replace Outdated Screenshot Reference in API-Auth Guide** Updates a single image reference in `docs/implementation-guides/api-auth/implement-api-auth.mdx` to point at the new Connect UI screenshot and adds the corresponding asset under `docs/images/connect-ui/`. No product code or logic is modified; scope is limited to documentation. <details> <summary><strong>Key Changes</strong></summary> • Replaced image link from `/images/screenshots/connect-integration-list.png` to `/images/connect-ui/integrations-list.png` • Added/updated static image assets under `docs/images/connect-ui/*` </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs/implementation-guides/api-auth/implement-api-auth.mdx` • `docs/images/connect-ui/*` </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: update screenshots to use new connect ui (#4839) ## Describe the problem and your solution - Update screenshots to use new connect ui <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Replace Outdated Screenshot Reference in API-Auth Guide** Updates a single image reference in `docs/implementation-guides/api-auth/implement-api-auth.mdx` to point at the new Connect UI screenshot and adds the corresponding asset under `docs/images/connect-ui/`. No product code or logic is modified; scope is limited to documentation. <details> <summary><strong>Key Changes</strong></summary> • Replaced image link from `/images/screenshots/connect-integration-list.png` to `/images/connect-ui/integrations-list.png` • Added/updated static image assets under `docs/images/connect-ui/*` </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs/implementation-guides/api-auth/implement-api-auth.mdx` • `docs/images/connect-ui/*` </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Update docs with connection tags feature (#5397) <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Document connection tagging lifecycle and migrate away from legacy end-user fields** Adds comprehensive documentation, reference updates, and OpenAPI/schema changes that formalize the new `tags` attribution model for connections while deprecating the legacy `end_user`/`organization` payloads. The PR introduces a dedicated connection tags guide, a migration walkthrough, refreshed SDK/API docs, regenerated integration snippets, and aligns the public spec with tag-based filtering and parameters. <details> <summary><strong>Key Changes</strong></summary> • Added `docs/implementation-guides/platform/auth/connection-tags.mdx` plus new ToC entries and screenshots to explain why and how to use connection tags, including filtering, webhook payloads, UI behavior, and update semantics. • Created `docs/implementation-guides/platform/migrations/migrate-from-end-user.mdx` detailing the transition path from `end_user` fields to tags, including webhook reconciliation logic and automatic backfill behavior. • Updated API/SDK references (e.g., `docs/reference/api/connect/sessions/create.mdx`, `docs/reference/api/connections/list.mdx`, `docs/reference/sdks/node.mdx`) and the OpenAPI spec (`docs/spec.yaml`) to add `tags` parameters, mark `end_user` properties as deprecated, and document tag-based query semantics. • Regenerated integration snippets and provider docs plus refreshed tool-calling guides so sample code now sets and queries tags instead of relying on `end_user` arguments. • Minor UI change in `packages/webapp/src/components/AvatarCustom.tsx` that currently logs `globalEnv` when computing organization avatars. </details> <details> <summary><strong>Affected Areas</strong></summary> • docs/implementation-guides/platform/auth/connection-tags.mdx • docs/implementation-guides/platform/migrations/migrate-from-end-user.mdx • docs/reference/sdks/node.mdx • docs/spec.yaml • docs/implementation-guides/use-cases/tool-calling/*.mdx • packages/webapp/src/components/AvatarCustom.tsx </details> --- *This summary was automatically generated by @propel-code-bot* | 7 个月前 | |
docs: Update docs with connection tags feature (#5397) <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Document connection tagging lifecycle and migrate away from legacy end-user fields** Adds comprehensive documentation, reference updates, and OpenAPI/schema changes that formalize the new `tags` attribution model for connections while deprecating the legacy `end_user`/`organization` payloads. The PR introduces a dedicated connection tags guide, a migration walkthrough, refreshed SDK/API docs, regenerated integration snippets, and aligns the public spec with tag-based filtering and parameters. <details> <summary><strong>Key Changes</strong></summary> • Added `docs/implementation-guides/platform/auth/connection-tags.mdx` plus new ToC entries and screenshots to explain why and how to use connection tags, including filtering, webhook payloads, UI behavior, and update semantics. • Created `docs/implementation-guides/platform/migrations/migrate-from-end-user.mdx` detailing the transition path from `end_user` fields to tags, including webhook reconciliation logic and automatic backfill behavior. • Updated API/SDK references (e.g., `docs/reference/api/connect/sessions/create.mdx`, `docs/reference/api/connections/list.mdx`, `docs/reference/sdks/node.mdx`) and the OpenAPI spec (`docs/spec.yaml`) to add `tags` parameters, mark `end_user` properties as deprecated, and document tag-based query semantics. • Regenerated integration snippets and provider docs plus refreshed tool-calling guides so sample code now sets and queries tags instead of relying on `end_user` arguments. • Minor UI change in `packages/webapp/src/components/AvatarCustom.tsx` that currently logs `globalEnv` when computing organization avatars. </details> <details> <summary><strong>Affected Areas</strong></summary> • docs/implementation-guides/platform/auth/connection-tags.mdx • docs/implementation-guides/platform/migrations/migrate-from-end-user.mdx • docs/reference/sdks/node.mdx • docs/spec.yaml • docs/implementation-guides/use-cases/tool-calling/*.mdx • packages/webapp/src/components/AvatarCustom.tsx </details> --- *This summary was automatically generated by @propel-code-bot* | 7 个月前 | |
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: sample app (#4920) ## Describe the problem and your solution - docs on sample app <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Consolidated Sample-App Documentation & Provider Doc Cleanup** This PR overhauls the sample-app documentation by expanding `docs/getting-started/sample-app.mdx` with multi-provider setup instructions (Slack, Google Drive, OneDrive Business & Personal) and a new *File Integration Guide* section. Redundant, provider-specific how-to blocks are removed from `google-drive.mdx`, `one-drive.mdx`, and `one-drive-personal.mdx`, each now pointing back to the central guide. Front-matter titles are corrected (e.g., `OneDrive` → `OneDrive for Business`), ~15 new screenshots are introduced, and the OneDrive logo SVG is updated. <details> <summary><strong>Key Changes</strong></summary> • Major rewrite of `docs/getting-started/sample-app.mdx` (+220/-80 LOC) incl. OAuth setups, env-vars, File Integration Guide with screenshots • Removed duplicated implementation guides from `google-drive.mdx`, `one-drive.mdx`, `one-drive-personal.mdx`; added *Complete Integration Implementation* section linking to sample-app • Fixed front-matter titles and sidebar labels for OneDrive for Business docs • Added ~15 assets under `docs/images/file-storage-integrations/` and updated image references • Replaced legacy `one-drive.svg` with new vector asset </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs/getting-started/sample-app.mdx` • `docs/integrations/all/google-drive.mdx` • `docs/integrations/all/one-drive.mdx` • `docs/integrations/all/one-drive-personal.mdx` • `docs/images/file-storage-integrations/*` • `packages/webapp/public/images/template-logos/one-drive.svg` </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 10 个月前 | ||
| 10 个月前 |
