| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat: add CreateFunction definition (#6664) Also remove the recent changes made around createWebhook. They will be folded and reintroduced as part of the function primitive initiative `function` definition types are in https://github.com/NangoHQ/nango/pull/6664/changes#diff-cedceb6eb8af423d2de17f68fed59bd218cf3c5029655359b4361d444c733256 The rest is reverting support for `createWebhook` in `runner-sdk` and `cli` <!-- Describe the problem and your solution --> <!-- 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/6664?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. --> | 3 个月前 | |
feat(cli): build and send json-schema per function (#5572) > Function aka "flow", "sync_config" We currently generate a "global" json schema with all the models in the integration folders and save it to `schema.json`. When deploying / generating docs / dry-running, we load that big schema and use it as the source of truth. We send the full json-schema for deploying, and let the server filter the schemas for each function (aka. sync_config, flow). Furthermore, we take a very convoluted path to generate `schema.json`: - Convert zod schemas to `NangoModel` - Use `NangoModel` to generate `schema.ts` - Use `ts-to-json-schema-generator` to generate `schema.json` from `schema.ts` In my previous PR, I made the server accept function-level json-schemas. Each function can now be sent with it's own json-schema, as opposed to a single top-level json-schema in `POST /sync/deploy`. This PR: - Keeps the generation of `schema.ts` and `schema.json` AS IS (adds a deprecation notice comment on `schema.ts`) - Updates zod versions in the `cli` and `runner-sdk` packages to v4.3.6 (currently latest) - Also updates zod version in `cli/example/package.json`. This is what will make our customers packages be updated as soon as a cli command is run. - Leverages `z.toJsonSchema` (introduced in zod v4) to generate json-schemas directly from the zod schemas. - Adds the json-schemas to each function in the payload. - Stops sending top-level json-schema with all models - Modifies dry-run and generate:docs to use these function-level json-schemas instead of `schema.json`. - These new json-schemas are generated and kept in-memory. They don't generate any artifacts. Every run of `deploy`, `dry-run` and `generate:docs` will re-generate them in-memory for use. The source is the compiled `cjs` files, and not the typescript files themselves. <!-- Summary by @propel-code-bot --> --- It also adjusts parsing and validation types to allow optional per-function json_schema fields and updates related tests/snapshots to match the new schema format expectations. --- *This summary was automatically generated by @propel-code-bot* | 6 个月前 | |
feat(cli): Allow init to create any directory name (#3338) <!-- Describe the problem and your solution --> - Allows any directory name. If no directory is given, init creates against the current directory, like git does. - Uses .nango directory as a sentinel for determining if it's a nango integration folder or not - Moves init into services directory for consistency - Moves several of the files that were created in init with template strings to be files in templates, also for consistency - Moves some tests around to be beside the init service - Updates some docs <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> | 1 年前 | |
feat(integrations): refractor apple-app-store and use JWT method instead (#6955) ## Describe the problem and your solution - `apple-app-store` used a bespoke `APP_STORE` auth mode that has been broken since it was originally introduced in #1464: it signed a JWT and then POSTed it to `https://api.appstoreconnect.apple.com/v1/apps` expecting a token back (`createCredentialsFromURL`). But App Store Connect has no token-exchange endpoint — the signed JWT *is* the access token, used directly as the Bearer credential on every request — and `/v1/apps` is a GET-only "list apps" endpoint, not something you can trade a JWT against. `tokenResponse.token` was always `undefined`, so no connection using this auth mode could ever have worked. - I checked prod and there are zero active `apple-app-store` connections, so there's no migration path to worry about, this removes the broken auth mode outright instead of patching it, and uses an auth mode we are currently using with other providers. <!-- 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/6955?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. --> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> | 1 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 个月前 | ||
| 6 个月前 | ||
| 1 年前 | ||
| 1 个月前 |