featurebase-node 0.15.1 → 0.15.2

package/resources/feedback/posts/insights.js

@@ -0,0 +1,269 @@
+"use strict";
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.Insights = void 0;
+const resource_1 = require("../../../core/resource.js");
+const pagination_1 = require("../../../core/pagination.js");
+const headers_1 = require("../../../internal/headers.js");
+const path_1 = require("../../../internal/utils/path.js");
+/**
+ * User-submitted feedback and feature requests. Posts belong to boards and can be upvoted, commented on, and tracked through statuses.
+ */
+class Insights extends resource_1.APIResource {
+    /**
+     * Returns the insights filed under the request `{id}` — the customer quotes kept
+     * as evidence for it. Newest first.
+     *
+     * Posts linked with `attachTo` are **not** listed here: they are posts, not
+     * insights, and they stay in `GET /v2/posts`. This endpoint lists exactly the rows
+     * that `POST /v2/posts/{insightId}/link-insight` filed under this request.
+     *
+     * ### Query parameters
+     *
+     * - `limit` — insights per page, 1–100. **Defaults to 100**, so most requests
+     *   return their whole evidence set in one call.
+     * - `cursor` — opaque cursor from a previous response's `nextCursor`.
+     *
+     * ### Response format
+     *
+     * The standard post list envelope:
+     *
+     * - `object` — always `"list"`
+     * - `data` — the insights, each in the same shape as any other post object, with
+     *   `kind: 'insight'` and `linkedIssueId` set to `{id}`
+     * - `nextCursor` — pass it back as `cursor` for the next page; `null` on the last
+     *   page
+     *
+     * `pagination` is never returned by this endpoint — it is cursor-paginated only.
+     *
+     * ### Notes
+     *
+     * - Pass the **request's** id, not an insight's. An id that is not a request (an
+     *   insight, or an unknown id in this workspace) is not an error: the list simply
+     *   comes back empty.
+     * - The insights returned are not readable through `GET /v2/posts/{insightId}` —
+     *   that endpoint serves work items only.
+     *
+     * @example
+     * ```ts
+     * // Automatically fetches more pages as needed.
+     * for await (const post of client.feedback.posts.insights.list(
+     *   '507f1f77bcf86cd799439011',
+     * )) {
+     *   // ...
+     * }
+     * ```
+     */
+    list(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion, ...query } = params ?? {};
+        return this._client.getAPIList((0, path_1.path) `/v2/posts/${id}/insights`, (pagination_1.CursorPage), {
+            query,
+            ...options,
+            headers: (0, headers_1.buildHeaders)([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * Promotes the insight `{id}` into a request of its own — the way back from
+     * `link-insight`.
+     *
+     * `kind` becomes `issue`, any link to another request is cleared (that request's
+     * `linkedInsightCount` is recounted), and the row is a post again:
+     * `GET /v2/posts/{id}` answers it, and `GET /v2/posts` lists it.
+     *
+     * The promoted request is given the workspace's default status if it had none, is
+     * filed on the internal board (its previous board is kept as the request's source
+     * category), and is created **hidden from the portal** — publish it with
+     * `PATCH /v2/posts/{id}` when you want customers to see it. It then announces
+     * itself like a freshly created request: the `post.created` webhook fires and the
+     * workspace's tracker integrations receive it, subject to the same rules as any
+     * other creation. Featurebase also looks for other existing insights that support
+     * the new request, in the background.
+     *
+     * Calling this on a post that is already a request is a no-op and returns it
+     * unchanged.
+     *
+     * ### Request
+     *
+     * No body. The insight is named by the path.
+     *
+     * ### Response
+     *
+     * The resulting request, in the standard post format.
+     *
+     * @example
+     * ```ts
+     * const post =
+     *   await client.feedback.posts.insights.convertToPost(
+     *     '507f1f77bcf86cd799439011',
+     *   );
+     * ```
+     */
+    convertToPost(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion } = params ?? {};
+        return this._client.post((0, path_1.path) `/v2/posts/${id}/convert-to-issue`, {
+            ...options,
+            headers: (0, headers_1.buildHeaders)([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * An **insight** is a customer's own words kept as evidence under a request — a
+     * quote, not a request of its own, and never returned by `GET /v2/posts`.
+     *
+     * This endpoint turns the post `{id}` into an insight under the request `issueId`.
+     * Use it for the sentence a customer actually said; use `attachTo` on
+     * `POST /v2/posts` when the thing you are filing is a request in its own right and
+     * should stay one.
+     *
+     * ### What changes
+     *
+     * - The post becomes an insight: `kind` is `insight` and `linkedIssueId` is the
+     *   request.
+     * - **It leaves the posts resource.** `GET /v2/posts/{id}` answers `404` from then
+     *   on, and it no longer appears in `GET /v2/posts`. Read it back through
+     *   `GET /v2/posts/{issueId}/insights`, which is where it now lives.
+     * - Its author counts as a supporter of the request: the insight's upvoters are
+     *   rolled onto the request (deduped by user, so a customer who had already voted
+     *   is not counted twice) and the insight's author is subscribed to the request's
+     *   updates. The request's `upvotes` goes up accordingly.
+     * - The request's `linkedInsightCount` is recounted from the live set of insights
+     *   pointing at it.
+     *
+     * Linking again to the same request is a no-op and returns the insight unchanged.
+     *
+     * An insight that is already filed under a DIFFERENT request is MOVED — but only
+     * if nobody has confirmed that first link by hand. The old link is dropped first,
+     * and the old request is remembered as "not a match" so automatic matching never
+     * puts it back there. An insight whose link was already confirmed by a person
+     * (every link made through this endpoint counts as confirmed) is refused with
+     * `400 Insight is already linked to another issue. Detach it first.` — call
+     * `POST /v2/posts/{id}/unlink-insight` first, then link it where you want it.
+     *
+     * ### Which targets are refused
+     *
+     * - `404` — no post with `{id}` in this workspace, or one the API key cannot see
+     *   (`Insight not found.`); no request with `issueId`, or one the API key cannot
+     *   see (`Issue not found.`).
+     * - `400` — `issueId` equals `{id}` (a post cannot be linked to itself); the
+     *   target is not a request (it is itself an insight, or a record — convert or
+     *   restore it first); the target is a processed submission (`atomizedAt` — link
+     *   to the requests that came out of it); the post being linked is a record (link
+     *   the record's extracted insights instead); the post is already filed under
+     *   another request by hand (unlink it first).
+     * - `400 invalid_id` — `{id}` or `issueId` is not a valid object id.
+     *
+     * A merged, held-for-moderation, spam-held or closed target is **not** refused
+     * here: those guards apply to automatic (AI) attachment only, and a person linking
+     * by hand is trusted to mean it.
+     *
+     * ### Response
+     *
+     * The updated insight, in the standard post format (`kind: 'insight'`,
+     * `linkedIssueId` set). The request it was linked to is not returned — fetch it
+     * with `GET /v2/posts/{issueId}` if you need its new `upvotes` and
+     * `linkedInsightCount`.
+     *
+     * ### Body
+     *
+     * - `issueId` — the request to file this post under. Required.
+     * - `linkSource` — deprecated and ignored; a link made through the API is always a
+     *   manual link.
+     *
+     * ### Errors
+     *
+     * Failures raised by the insight service (404 / 400 / 409) are returned as
+     * `{ "code": <status>, "message": "..." }` rather than in the Stripe-style
+     * envelope the rest of this resource uses. The status code is the contract; do not
+     * parse the body shape.
+     *
+     * @example
+     * ```ts
+     * const post = await client.feedback.posts.insights.link(
+     *   '507f1f77bcf86cd799439011',
+     *   { issueId: '507f1f77bcf86cd799439011' },
+     * );
+     * ```
+     */
+    link(id, params, options) {
+        const { 'Featurebase-Version': featurebaseVersion, ...body } = params;
+        return this._client.post((0, path_1.path) `/v2/posts/${id}/link-insight`, {
+            body,
+            ...options,
+            headers: (0, headers_1.buildHeaders)([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * Detaches the insight `{id}` from the request it was filed under.
+     *
+     * **The row stays an insight** — the customer's words do not disappear, they just
+     * return to the unlinked pool. `linkedIssueId` becomes `null`, and
+     * `GET /v2/posts/{id}` still answers `404`: an unlinked insight is still not a
+     * post. To get a post back, call `POST /v2/posts/{id}/convert-to-issue`.
+     *
+     * ### What does NOT change
+     *
+     * The votes this insight rolled onto the request are **not** taken back, and the
+     * author stays subscribed to it. They are real demand that was expressed, and the
+     * roll-up was deduplicated against votes the customer may have cast independently
+     * — unwinding it would remove votes it never created. The request's `upvotes`
+     * therefore stays where the link left it. Its `linkedInsightCount` IS recounted
+     * and goes down.
+     *
+     * The request that was just unlinked is remembered as "not a match" for this
+     * insight, so automatic matching never files it there again.
+     *
+     * Calling this on a post that is not an insight, or on an insight that is already
+     * unlinked, is a no-op and returns the row unchanged.
+     *
+     * ### Request
+     *
+     * No body. The insight is named by the path.
+     *
+     * ### Response
+     *
+     * The updated insight, in the standard post format.
+     *
+     * @example
+     * ```ts
+     * const post = await client.feedback.posts.insights.unlink(
+     *   '507f1f77bcf86cd799439011',
+     * );
+     * ```
+     */
+    unlink(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion } = params ?? {};
+        return this._client.post((0, path_1.path) `/v2/posts/${id}/unlink-insight`, {
+            ...options,
+            headers: (0, headers_1.buildHeaders)([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+}
+exports.Insights = Insights;
+//# sourceMappingURL=insights.js.map

package/resources/feedback/posts/insights.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"insights.js","sourceRoot":"","sources":["../../../src/resources/feedback/posts/insights.ts"],"names":[],"mappings":";AAAA,sFAAsF;;;AAEtF,wDAAqD;AAIrD,4DAA0F;AAC1F,0DAAyD;AAEzD,0DAAoD;AAEpD;;GAEG;AACH,MAAa,QAAS,SAAQ,sBAAW;IACvC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA2CG;IACH,IAAI,CACF,EAAU,EACV,SAA+C,EAAE,EACjD,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,KAAK,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QAC7E,OAAO,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,IAAA,WAAI,EAAA,aAAa,EAAE,WAAW,EAAE,CAAA,uBAAyB,CAAA,EAAE;YACxF,KAAK;YACL,GAAG,OAAO;YACV,OAAO,EAAE,IAAA,sBAAY,EAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAmCG;IACH,aAAa,CACX,EAAU,EACV,SAAwD,EAAE,EAC1D,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QACnE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAA,WAAI,EAAA,aAAa,EAAE,mBAAmB,EAAE;YAC/D,GAAG,OAAO;YACV,OAAO,EAAE,IAAA,sBAAY,EAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA6EG;IACH,IAAI,CAAC,EAAU,EAAE,MAAyB,EAAE,OAAwB;QAClE,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,IAAI,EAAE,GAAG,MAAM,CAAC;QACtE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAA,WAAI,EAAA,aAAa,EAAE,eAAe,EAAE;YAC3D,IAAI;YACJ,GAAG,OAAO;YACV,OAAO,EAAE,IAAA,sBAAY,EAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAqCG;IACH,MAAM,CACJ,EAAU,EACV,SAAiD,EAAE,EACnD,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QACnE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAA,WAAI,EAAA,aAAa,EAAE,iBAAiB,EAAE;YAC7D,GAAG,OAAO;YACV,OAAO,EAAE,IAAA,sBAAY,EAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;CACF;AA9QD,4BA8QC"}

package/resources/feedback/posts/insights.mjs

@@ -0,0 +1,265 @@
+// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
+import { APIResource } from "../../../core/resource.mjs";
+import { CursorPage } from "../../../core/pagination.mjs";
+import { buildHeaders } from "../../../internal/headers.mjs";
+import { path } from "../../../internal/utils/path.mjs";
+/**
+ * User-submitted feedback and feature requests. Posts belong to boards and can be upvoted, commented on, and tracked through statuses.
+ */
+export class Insights extends APIResource {
+    /**
+     * Returns the insights filed under the request `{id}` — the customer quotes kept
+     * as evidence for it. Newest first.
+     *
+     * Posts linked with `attachTo` are **not** listed here: they are posts, not
+     * insights, and they stay in `GET /v2/posts`. This endpoint lists exactly the rows
+     * that `POST /v2/posts/{insightId}/link-insight` filed under this request.
+     *
+     * ### Query parameters
+     *
+     * - `limit` — insights per page, 1–100. **Defaults to 100**, so most requests
+     *   return their whole evidence set in one call.
+     * - `cursor` — opaque cursor from a previous response's `nextCursor`.
+     *
+     * ### Response format
+     *
+     * The standard post list envelope:
+     *
+     * - `object` — always `"list"`
+     * - `data` — the insights, each in the same shape as any other post object, with
+     *   `kind: 'insight'` and `linkedIssueId` set to `{id}`
+     * - `nextCursor` — pass it back as `cursor` for the next page; `null` on the last
+     *   page
+     *
+     * `pagination` is never returned by this endpoint — it is cursor-paginated only.
+     *
+     * ### Notes
+     *
+     * - Pass the **request's** id, not an insight's. An id that is not a request (an
+     *   insight, or an unknown id in this workspace) is not an error: the list simply
+     *   comes back empty.
+     * - The insights returned are not readable through `GET /v2/posts/{insightId}` —
+     *   that endpoint serves work items only.
+     *
+     * @example
+     * ```ts
+     * // Automatically fetches more pages as needed.
+     * for await (const post of client.feedback.posts.insights.list(
+     *   '507f1f77bcf86cd799439011',
+     * )) {
+     *   // ...
+     * }
+     * ```
+     */
+    list(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion, ...query } = params ?? {};
+        return this._client.getAPIList(path `/v2/posts/${id}/insights`, (CursorPage), {
+            query,
+            ...options,
+            headers: buildHeaders([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * Promotes the insight `{id}` into a request of its own — the way back from
+     * `link-insight`.
+     *
+     * `kind` becomes `issue`, any link to another request is cleared (that request's
+     * `linkedInsightCount` is recounted), and the row is a post again:
+     * `GET /v2/posts/{id}` answers it, and `GET /v2/posts` lists it.
+     *
+     * The promoted request is given the workspace's default status if it had none, is
+     * filed on the internal board (its previous board is kept as the request's source
+     * category), and is created **hidden from the portal** — publish it with
+     * `PATCH /v2/posts/{id}` when you want customers to see it. It then announces
+     * itself like a freshly created request: the `post.created` webhook fires and the
+     * workspace's tracker integrations receive it, subject to the same rules as any
+     * other creation. Featurebase also looks for other existing insights that support
+     * the new request, in the background.
+     *
+     * Calling this on a post that is already a request is a no-op and returns it
+     * unchanged.
+     *
+     * ### Request
+     *
+     * No body. The insight is named by the path.
+     *
+     * ### Response
+     *
+     * The resulting request, in the standard post format.
+     *
+     * @example
+     * ```ts
+     * const post =
+     *   await client.feedback.posts.insights.convertToPost(
+     *     '507f1f77bcf86cd799439011',
+     *   );
+     * ```
+     */
+    convertToPost(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion } = params ?? {};
+        return this._client.post(path `/v2/posts/${id}/convert-to-issue`, {
+            ...options,
+            headers: buildHeaders([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * An **insight** is a customer's own words kept as evidence under a request — a
+     * quote, not a request of its own, and never returned by `GET /v2/posts`.
+     *
+     * This endpoint turns the post `{id}` into an insight under the request `issueId`.
+     * Use it for the sentence a customer actually said; use `attachTo` on
+     * `POST /v2/posts` when the thing you are filing is a request in its own right and
+     * should stay one.
+     *
+     * ### What changes
+     *
+     * - The post becomes an insight: `kind` is `insight` and `linkedIssueId` is the
+     *   request.
+     * - **It leaves the posts resource.** `GET /v2/posts/{id}` answers `404` from then
+     *   on, and it no longer appears in `GET /v2/posts`. Read it back through
+     *   `GET /v2/posts/{issueId}/insights`, which is where it now lives.
+     * - Its author counts as a supporter of the request: the insight's upvoters are
+     *   rolled onto the request (deduped by user, so a customer who had already voted
+     *   is not counted twice) and the insight's author is subscribed to the request's
+     *   updates. The request's `upvotes` goes up accordingly.
+     * - The request's `linkedInsightCount` is recounted from the live set of insights
+     *   pointing at it.
+     *
+     * Linking again to the same request is a no-op and returns the insight unchanged.
+     *
+     * An insight that is already filed under a DIFFERENT request is MOVED — but only
+     * if nobody has confirmed that first link by hand. The old link is dropped first,
+     * and the old request is remembered as "not a match" so automatic matching never
+     * puts it back there. An insight whose link was already confirmed by a person
+     * (every link made through this endpoint counts as confirmed) is refused with
+     * `400 Insight is already linked to another issue. Detach it first.` — call
+     * `POST /v2/posts/{id}/unlink-insight` first, then link it where you want it.
+     *
+     * ### Which targets are refused
+     *
+     * - `404` — no post with `{id}` in this workspace, or one the API key cannot see
+     *   (`Insight not found.`); no request with `issueId`, or one the API key cannot
+     *   see (`Issue not found.`).
+     * - `400` — `issueId` equals `{id}` (a post cannot be linked to itself); the
+     *   target is not a request (it is itself an insight, or a record — convert or
+     *   restore it first); the target is a processed submission (`atomizedAt` — link
+     *   to the requests that came out of it); the post being linked is a record (link
+     *   the record's extracted insights instead); the post is already filed under
+     *   another request by hand (unlink it first).
+     * - `400 invalid_id` — `{id}` or `issueId` is not a valid object id.
+     *
+     * A merged, held-for-moderation, spam-held or closed target is **not** refused
+     * here: those guards apply to automatic (AI) attachment only, and a person linking
+     * by hand is trusted to mean it.
+     *
+     * ### Response
+     *
+     * The updated insight, in the standard post format (`kind: 'insight'`,
+     * `linkedIssueId` set). The request it was linked to is not returned — fetch it
+     * with `GET /v2/posts/{issueId}` if you need its new `upvotes` and
+     * `linkedInsightCount`.
+     *
+     * ### Body
+     *
+     * - `issueId` — the request to file this post under. Required.
+     * - `linkSource` — deprecated and ignored; a link made through the API is always a
+     *   manual link.
+     *
+     * ### Errors
+     *
+     * Failures raised by the insight service (404 / 400 / 409) are returned as
+     * `{ "code": <status>, "message": "..." }` rather than in the Stripe-style
+     * envelope the rest of this resource uses. The status code is the contract; do not
+     * parse the body shape.
+     *
+     * @example
+     * ```ts
+     * const post = await client.feedback.posts.insights.link(
+     *   '507f1f77bcf86cd799439011',
+     *   { issueId: '507f1f77bcf86cd799439011' },
+     * );
+     * ```
+     */
+    link(id, params, options) {
+        const { 'Featurebase-Version': featurebaseVersion, ...body } = params;
+        return this._client.post(path `/v2/posts/${id}/link-insight`, {
+            body,
+            ...options,
+            headers: buildHeaders([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+    /**
+     * Detaches the insight `{id}` from the request it was filed under.
+     *
+     * **The row stays an insight** — the customer's words do not disappear, they just
+     * return to the unlinked pool. `linkedIssueId` becomes `null`, and
+     * `GET /v2/posts/{id}` still answers `404`: an unlinked insight is still not a
+     * post. To get a post back, call `POST /v2/posts/{id}/convert-to-issue`.
+     *
+     * ### What does NOT change
+     *
+     * The votes this insight rolled onto the request are **not** taken back, and the
+     * author stays subscribed to it. They are real demand that was expressed, and the
+     * roll-up was deduplicated against votes the customer may have cast independently
+     * — unwinding it would remove votes it never created. The request's `upvotes`
+     * therefore stays where the link left it. Its `linkedInsightCount` IS recounted
+     * and goes down.
+     *
+     * The request that was just unlinked is remembered as "not a match" for this
+     * insight, so automatic matching never files it there again.
+     *
+     * Calling this on a post that is not an insight, or on an insight that is already
+     * unlinked, is a no-op and returns the row unchanged.
+     *
+     * ### Request
+     *
+     * No body. The insight is named by the path.
+     *
+     * ### Response
+     *
+     * The updated insight, in the standard post format.
+     *
+     * @example
+     * ```ts
+     * const post = await client.feedback.posts.insights.unlink(
+     *   '507f1f77bcf86cd799439011',
+     * );
+     * ```
+     */
+    unlink(id, params = {}, options) {
+        const { 'Featurebase-Version': featurebaseVersion } = params ?? {};
+        return this._client.post(path `/v2/posts/${id}/unlink-insight`, {
+            ...options,
+            headers: buildHeaders([
+                {
+                    ...(featurebaseVersion?.toString() != null ?
+                        { 'Featurebase-Version': featurebaseVersion?.toString() }
+                        : undefined),
+                },
+                options?.headers,
+            ]),
+        });
+    }
+}
+//# sourceMappingURL=insights.mjs.map

package/resources/feedback/posts/insights.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"insights.mjs","sourceRoot":"","sources":["../../../src/resources/feedback/posts/insights.ts"],"names":[],"mappings":"AAAA,sFAAsF;AAEtF,OAAO,EAAE,WAAW,EAAE,mCAA+B;AAIrD,OAAO,EAAE,UAAU,EAAsC,qCAAiC;AAC1F,OAAO,EAAE,YAAY,EAAE,sCAAkC;AAEzD,OAAO,EAAE,IAAI,EAAE,yCAAqC;AAEpD;;GAEG;AACH,MAAM,OAAO,QAAS,SAAQ,WAAW;IACvC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA2CG;IACH,IAAI,CACF,EAAU,EACV,SAA+C,EAAE,EACjD,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,KAAK,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QAC7E,OAAO,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,IAAI,CAAA,aAAa,EAAE,WAAW,EAAE,CAAA,UAAyB,CAAA,EAAE;YACxF,KAAK;YACL,GAAG,OAAO;YACV,OAAO,EAAE,YAAY,CAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAmCG;IACH,aAAa,CACX,EAAU,EACV,SAAwD,EAAE,EAC1D,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QACnE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAI,CAAA,aAAa,EAAE,mBAAmB,EAAE;YAC/D,GAAG,OAAO;YACV,OAAO,EAAE,YAAY,CAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA6EG;IACH,IAAI,CAAC,EAAU,EAAE,MAAyB,EAAE,OAAwB;QAClE,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,IAAI,EAAE,GAAG,MAAM,CAAC;QACtE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAI,CAAA,aAAa,EAAE,eAAe,EAAE;YAC3D,IAAI;YACJ,GAAG,OAAO;YACV,OAAO,EAAE,YAAY,CAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAqCG;IACH,MAAM,CACJ,EAAU,EACV,SAAiD,EAAE,EACnD,OAAwB;QAExB,MAAM,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,GAAG,MAAM,IAAI,EAAE,CAAC;QACnE,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,IAAI,CAAA,aAAa,EAAE,iBAAiB,EAAE;YAC7D,GAAG,OAAO;YACV,OAAO,EAAE,YAAY,CAAC;gBACpB;oBACE,GAAG,CAAC,kBAAkB,EAAE,QAAQ,EAAE,IAAI,IAAI,CAAC,CAAC;wBAC1C,EAAE,qBAAqB,EAAE,kBAAkB,EAAE,QAAQ,EAAE,EAAE;wBAC3D,CAAC,CAAC,SAAS,CAAC;iBACb;gBACD,OAAO,EAAE,OAAO;aACjB,CAAC;SACH,CAAC,CAAC;IACL,CAAC;CACF"}