@enrichlayer/el-linear 1.9.0 → 1.15.0

package/dist/queries/issues.js

@@ -41,12 +41,23 @@ export const FILTERED_SEARCH_ISSUES_QUERY = `
     }
   }
 `;
+/**
+ * Batch-resolves a search's team/project/assignee/delegate filter inputs.
+ *
+ * The `projects` block is `@include`-gated: Linear treats a null filter
+ * comparator as "no filter", so an always-on block with an unset
+ * `$projectName` would fetch an arbitrary project. (Search resolves a UUID
+ * `--project` directly without consulting this block, so only the
+ * name-resolution arm is needed here.)
+ */
 export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
   query BatchResolveForSearch(
     $teamKey: String
     $teamName: String
     $projectName: String
+    $hasProjectName: Boolean = false
     $assigneeEmail: String
+    $delegateEmail: String
   ) {
     teams(
       filter: {
@@ -64,7 +75,10 @@ export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
       }
     }
 
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
       nodes {
         id
         name
@@ -78,6 +92,14 @@ export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
         email
       }
     }
+
+    delegates: users(filter: { email: { eq: $delegateEmail } }, first: 1) {
+      nodes {
+        id
+        name
+        email
+      }
+    }
   }
 `;
 export const GET_ISSUE_BY_ID_QUERY = `
@@ -102,14 +124,46 @@ export const GET_ISSUE_BY_IDENTIFIER_QUERY = `
     }
   }
 `;
+/**
+ * Batch-resolves an update's project/milestone/issue inputs.
+ *
+ * The project and milestone blocks are `@include`-gated for the same
+ * reason as `BATCH_RESOLVE_FOR_CREATE_QUERY`: a null filter comparator is
+ * a no-op that returns an arbitrary record. A UUID `--project` is resolved
+ * by `id` (`projectsById`) so its milestones are still fetched for
+ * `--project-milestone` name resolution; a name uses `projectsByName`.
+ */
 export const BATCH_RESOLVE_FOR_UPDATE_QUERY = `
   query BatchResolveForUpdate(
     $projectName: String
+    $projectId: ID
+    $hasProjectName: Boolean = false
+    $hasProjectId: Boolean = false
     $teamKey: String
     $issueNumber: Float
     $milestoneName: String
+    $hasMilestoneName: Boolean = false
   ) {
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projectsByName: projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
+      nodes {
+        id
+        name
+        projectMilestones {
+          nodes {
+            id
+            name
+          }
+        }
+      }
+    }
+
+    projectsById: projects(
+      filter: { id: { eq: $projectId } }
+      first: 1
+    ) @include(if: $hasProjectId) {
       nodes {
         id
         name
@@ -125,7 +179,7 @@ export const BATCH_RESOLVE_FOR_UPDATE_QUERY = `
     milestones: projectMilestones(
       filter: { name: { eq: $milestoneName } }
       first: 1
-    ) {
+    ) @include(if: $hasMilestoneName) {
       nodes {
         id
         name
@@ -187,14 +241,59 @@ export const UPDATE_ISSUE_MUTATION = `
     }
   }
 `;
+export const ARCHIVE_ISSUE_MUTATION = `
+  mutation ArchiveIssue($id: String!) {
+    issueArchive(id: $id) {
+      success
+      lastSyncId
+      entity {
+        id
+      }
+    }
+  }
+`;
+export const DELETE_ISSUE_MUTATION = `
+  mutation DeleteIssue($id: String!, $permanentlyDelete: Boolean) {
+    issueDelete(id: $id, permanentlyDelete: $permanentlyDelete) {
+      success
+      lastSyncId
+      entity {
+        id
+      }
+    }
+  }
+`;
+/**
+ * Batch-resolves a create's team/project/milestone/parent inputs in one
+ * round-trip.
+ *
+ * The project and milestone blocks are gated behind `@include` directives
+ * rather than left always-on. Linear treats a null filter comparator
+ * (`{ name: { eqIgnoreCase: null } }`) as "no filter" — so an always-on
+ * `projects` block with an unset `$projectName` returns an *arbitrary*
+ * project, which the caller would then mistake for the user's project
+ * (e.g. auto-switching the team to that unrelated project's team). The
+ * `has*` booleans ensure a block is fetched only when its input exists.
+ *
+ * A UUID `--project` is resolved by `id` (`projectsById`) so its team
+ * associations are still fetched for team-project validation; a name is
+ * resolved by `name` (`projectsByName`). The two are mutually exclusive,
+ * but GraphQL forbids two same-aliased fields with differing arguments,
+ * so they carry distinct aliases and the service folds whichever ran
+ * into `resolveResult.projects`.
+ */
 export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
   query BatchResolveForCreate(
     $teamKey: String
     $teamName: String
     $projectName: String
+    $projectId: ID
+    $hasProjectName: Boolean = false
+    $hasProjectId: Boolean = false
     $parentTeamKey: String
     $parentIssueNumber: Float
     $milestoneName: String
+    $hasMilestoneName: Boolean = false
   ) {
     teams(
       filter: {
@@ -212,7 +311,26 @@ export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
       }
     }
 
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projectsByName: projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
+      nodes {
+        id
+        name
+        teams {
+          nodes { id key }
+        }
+        projectMilestones {
+          nodes { id name }
+        }
+      }
+    }
+
+    projectsById: projects(
+      filter: { id: { eq: $projectId } }
+      first: 1
+    ) @include(if: $hasProjectId) {
       nodes {
         id
         name
@@ -228,7 +346,7 @@ export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
     milestones: projectMilestones(
       filter: { name: { eq: $milestoneName } }
       first: 1
-    ) {
+    ) @include(if: $hasMilestoneName) {
       nodes {
         id
         name
@@ -310,6 +428,30 @@ export const GET_ISSUE_TEAM_QUERY = `
     }
   }
 `;
+export const GET_ISSUE_START_CONTEXT_QUERY = `
+  query GetIssueStartContext($id: String!) {
+    issue(id: $id) {
+      id
+      identifier
+      state { id name type }
+      team { id key name }
+      delegate { id name url }
+    }
+  }
+`;
+export const TEAM_STARTED_STATUSES_QUERY = `
+  query TeamStartedStatuses($teamId: String!) {
+    team(id: $teamId) {
+      states(filter: { type: { eq: "started" } }) {
+        nodes {
+          id
+          name
+          position
+        }
+      }
+    }
+  }
+`;
 export const ISSUE_RELATION_CREATE_MUTATION = `
   mutation IssueRelationCreate($input: IssueRelationCreateInput!) {
     issueRelationCreate(input: $input) {

package/dist/queries/labels-types.d.ts

@@ -0,0 +1,65 @@
+/**
+ * Typed response shapes for the queries in `./labels.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+interface LabelTeamRef {
+    id: string;
+    key: string;
+    name: string;
+}
+interface LabelParentRef {
+    id: string;
+    name: string;
+}
+/** Mirrors the issueLabel selection set on `CREATE_LABEL_MUTATION`. */
+interface CreatedLabelNode {
+    id: string;
+    name: string;
+    color: string;
+    team: LabelTeamRef | null;
+    parent: LabelParentRef | null;
+}
+/** Mirrors the issueLabel selection set on `RETIRE_LABEL_MUTATION`. */
+interface RetiredLabelNode {
+    id: string;
+    name: string;
+    color: string;
+    retiredAt: string | null;
+    team: LabelTeamRef | null;
+}
+/** Mirrors the issueLabel selection set on `RESTORE_LABEL_MUTATION`. */
+interface RestoredLabelNode {
+    id: string;
+    name: string;
+    color: string;
+    team: LabelTeamRef | null;
+}
+interface ParentLabelNode {
+    id: string;
+    name: string;
+    isGroup: boolean;
+}
+export interface FindParentLabelResponse {
+    issueLabels: {
+        nodes: ParentLabelNode[];
+    };
+}
+export interface CreateLabelResponse {
+    issueLabelCreate: {
+        success: boolean;
+        issueLabel: CreatedLabelNode | null;
+    };
+}
+export interface RetireLabelResponse {
+    issueLabelRetire: {
+        success: boolean;
+        issueLabel: RetiredLabelNode | null;
+    };
+}
+export interface RestoreLabelResponse {
+    issueLabelRestore: {
+        success: boolean;
+        issueLabel: RestoredLabelNode | null;
+    };
+}
+export {};

package/dist/queries/labels-types.js

@@ -0,0 +1,5 @@
+/**
+ * Typed response shapes for the queries in `./labels.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+export {};

package/dist/queries/project-milestones-types.d.ts

@@ -0,0 +1,92 @@
+/**
+ * Typed response shapes for the queries in `./project-milestones.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ *
+ * The selection sets vary across queries — some include `description`
+ * + `createdAt`, others only the lookup-relevant fields. Modelled as
+ * a base `MilestoneBaseRef` with extension shapes per query so each
+ * consumer reads only what was actually selected.
+ */
+import type { IssueNode } from "./issues-types.js";
+interface MilestoneProjectRef {
+    id: string;
+    name: string;
+}
+/**
+ * Mirrors the milestone selection set in `LIST_PROJECT_MILESTONES_QUERY`
+ * — full milestone fields without the project-back-reference.
+ */
+interface MilestoneListNode {
+    id: string;
+    name: string;
+    description: string | null;
+    targetDate: string | null;
+    sortOrder: number;
+    createdAt: string;
+    updatedAt: string;
+}
+/**
+ * Mirrors the milestone selection set in `GET_PROJECT_MILESTONE_BY_ID_QUERY`
+ * — list shape + project + issues connection.
+ */
+interface MilestoneDetailNode extends MilestoneListNode {
+    project: MilestoneProjectRef;
+    issues: {
+        nodes: IssueNode[];
+    };
+}
+/**
+ * Mirrors the milestone selection set in `FIND_PROJECT_MILESTONE_BY_NAME_*`
+ * — minimal lookup shape with project back-reference.
+ */
+export interface MilestoneLookupNode {
+    id: string;
+    name: string;
+    targetDate: string | null;
+    sortOrder: number;
+    project: MilestoneProjectRef;
+}
+/**
+ * Mirrors the milestone selection set on the create / update mutations —
+ * list shape + project (no issues connection).
+ */
+interface MutatedMilestoneNode extends MilestoneListNode {
+    project: MilestoneProjectRef;
+}
+export interface ListProjectMilestonesResponse {
+    project: {
+        id: string;
+        name: string;
+        projectMilestones: {
+            nodes: MilestoneListNode[];
+        };
+    } | null;
+}
+export interface GetProjectMilestoneByIdResponse {
+    projectMilestone: MilestoneDetailNode | null;
+}
+export interface FindProjectMilestoneScopedResponse {
+    project: {
+        projectMilestones: {
+            nodes: MilestoneLookupNode[];
+        };
+    } | null;
+}
+export interface FindProjectMilestoneGlobalResponse {
+    projectMilestones: {
+        nodes: MilestoneLookupNode[];
+    };
+}
+export interface CreateProjectMilestoneResponse {
+    projectMilestoneCreate: {
+        success: boolean;
+        projectMilestone: MutatedMilestoneNode | null;
+    };
+}
+export interface UpdateProjectMilestoneResponse {
+    projectMilestoneUpdate: {
+        success: boolean;
+        projectMilestone: MutatedMilestoneNode | null;
+    };
+}
+export {};

package/dist/queries/project-milestones-types.js

@@ -0,0 +1,10 @@
+/**
+ * Typed response shapes for the queries in `./project-milestones.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ *
+ * The selection sets vary across queries — some include `description`
+ * + `createdAt`, others only the lookup-relevant fields. Modelled as
+ * a base `MilestoneBaseRef` with extension shapes per query so each
+ * consumer reads only what was actually selected.
+ */
+export {};

package/dist/queries/project-milestones.d.ts

@@ -1,5 +1,5 @@
 export declare const LIST_PROJECT_MILESTONES_QUERY = "\n  query ListProjectMilestones($projectId: String!, $first: Int!) {\n    project(id: $projectId) {\n      id\n      name\n      projectMilestones(first: $first) {\n        nodes {\n          id\n          name\n          description\n          targetDate\n          sortOrder\n          createdAt\n          updatedAt\n        }\n      }\n    }\n  }\n";
-export declare const GET_PROJECT_MILESTONE_BY_ID_QUERY = "\n  query GetProjectMilestone($id: String!, $issuesFirst: Int) {\n    projectMilestone(id: $id) {\n      id\n      name\n      description\n      targetDate\n      sortOrder\n      createdAt\n      updatedAt\n      project {\n        id\n        name\n      }\n      issues(first: $issuesFirst) {\n        nodes {\n          \n  \n  id\n  identifier\n  title\n  description\n  summary { content generationStatus }\n  branchName\n  priority\n  estimate\n  dueDate\n  url\n  createdAt\n  updatedAt\n\n  \n  state {\n    id\n    name\n  }\n\n  \n  assignee {\n    id\n    name\n    url\n  }\n\n  \n  team {\n    id\n    key\n    name\n  }\n\n  \n  project {\n    id\n    name\n  }\n\n  \n  labels {\n    nodes {\n      id\n      name\n    }\n  }\n\n  \n  cycle {\n    id\n    name\n    number\n  }\n\n  \n  projectMilestone {\n    id\n    name\n    targetDate\n  }\n\n  \n  parent {\n    id\n    identifier\n    title\n  }\n\n  \n  children {\n    nodes {\n      id\n      identifier\n      title\n    }\n  }\n\n\n        }\n      }\n    }\n  }\n";
+export declare const GET_PROJECT_MILESTONE_BY_ID_QUERY = "\n  query GetProjectMilestone($id: String!, $issuesFirst: Int) {\n    projectMilestone(id: $id) {\n      id\n      name\n      description\n      targetDate\n      sortOrder\n      createdAt\n      updatedAt\n      project {\n        id\n        name\n      }\n      issues(first: $issuesFirst) {\n        nodes {\n          \n  \n  id\n  identifier\n  title\n  description\n  summary { content generationStatus }\n  branchName\n  priority\n  estimate\n  dueDate\n  url\n  createdAt\n  updatedAt\n\n  \n  state {\n    id\n    name\n  }\n\n  \n  assignee {\n    id\n    name\n    url\n  }\n\n  \n  delegate {\n    id\n    name\n    url\n  }\n\n  \n  team {\n    id\n    key\n    name\n  }\n\n  \n  project {\n    id\n    name\n  }\n\n  \n  labels {\n    nodes {\n      id\n      name\n    }\n  }\n\n  \n  cycle {\n    id\n    name\n    number\n  }\n\n  \n  projectMilestone {\n    id\n    name\n    targetDate\n  }\n\n  \n  parent {\n    id\n    identifier\n    title\n  }\n\n  \n  children {\n    nodes {\n      id\n      identifier\n      title\n    }\n  }\n\n\n        }\n      }\n    }\n  }\n";
 export declare const FIND_PROJECT_MILESTONE_BY_NAME_SCOPED = "\n  query FindProjectMilestoneScoped($name: String!, $projectId: String!) {\n    project(id: $projectId) {\n      projectMilestones(filter: { name: { eq: $name } }, first: 10) {\n        nodes {\n          id\n          name\n          targetDate\n          sortOrder\n          project {\n            id\n            name\n          }\n        }\n      }\n    }\n  }\n";
 export declare const FIND_PROJECT_MILESTONE_BY_NAME_GLOBAL = "\n  query FindProjectMilestoneGlobal($name: String!) {\n    projectMilestones(filter: { name: { eq: $name } }, first: 10) {\n      nodes {\n        id\n        name\n        targetDate\n        sortOrder\n        project {\n          id\n          name\n        }\n      }\n    }\n  }\n";
 export declare const CREATE_PROJECT_MILESTONE_MUTATION = "\n  mutation CreateProjectMilestone($projectId: String!, $name: String!, $description: String, $targetDate: TimelessDate) {\n    projectMilestoneCreate(input: {\n      projectId: $projectId\n      name: $name\n      description: $description\n      targetDate: $targetDate\n    }) {\n      success\n      projectMilestone {\n        id\n        name\n        description\n        targetDate\n        sortOrder\n        createdAt\n        updatedAt\n        project {\n          id\n          name\n        }\n      }\n    }\n  }\n";

package/dist/queries/projects-types.d.ts

@@ -0,0 +1,76 @@
+/**
+ * Typed response shapes for the queries in `./projects.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+interface ProjectTeamRef {
+    id: string;
+    key: string;
+    name: string;
+}
+interface ProjectBaseNode {
+    id: string;
+    name: string;
+    teams: {
+        nodes: ProjectTeamRef[];
+    };
+}
+/**
+ * Mirrors the project selection set used by `SEARCH_PROJECTS_BY_NAME_QUERY`
+ * and `CREATE_PROJECT_MUTATION` — base fields + state.
+ */
+interface ProjectWithStateNode extends ProjectBaseNode {
+    state: string;
+}
+interface ProjectIssueRef {
+    id: string;
+    identifier: string;
+    title: string;
+}
+interface ProjectWithIssuesNode extends ProjectBaseNode {
+    issues: {
+        nodes: ProjectIssueRef[];
+    };
+}
+export interface ProjectByIdResponse {
+    project: ProjectBaseNode | null;
+}
+export interface GetProjectResponse {
+    projects: {
+        nodes: ProjectBaseNode[];
+    };
+}
+export interface GetProjectTeamIssuesResponse {
+    project: ProjectWithIssuesNode | null;
+}
+export interface SearchProjectsByNameResponse {
+    projects: {
+        nodes: ProjectWithStateNode[];
+    };
+}
+export interface CreateProjectResponse {
+    projectCreate: {
+        success: boolean;
+        project: ProjectWithStateNode | null;
+    };
+}
+export interface UpdateProjectResponse {
+    projectUpdate: {
+        success: boolean;
+        project: ProjectBaseNode | null;
+    };
+}
+interface ProjectArchiveEntity {
+    id: string;
+}
+interface ProjectArchivePayload {
+    success: boolean;
+    lastSyncId: number;
+    entity: ProjectArchiveEntity | null;
+}
+export interface ArchiveProjectResponse {
+    projectArchive: ProjectArchivePayload;
+}
+export interface DeleteProjectResponse {
+    projectDelete: ProjectArchivePayload;
+}
+export {};

package/dist/queries/projects-types.js

@@ -0,0 +1,5 @@
+/**
+ * Typed response shapes for the queries in `./projects.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+export {};

package/dist/queries/projects.d.ts

@@ -5,3 +5,5 @@ export declare const GET_PROJECT_TEAM_ISSUES_QUERY = "\n  query GetProjectTeamIs
 export declare const SEARCH_PROJECTS_BY_NAME_QUERY = "\n  query SearchProjectsByName($name: String!) {\n    projects(filter: { name: { containsIgnoreCase: $name } }, first: 10) {\n      nodes {\n        id\n        name\n        state\n        teams {\n          nodes { id key name }\n        }\n      }\n    }\n  }\n";
 export declare const CREATE_PROJECT_MUTATION = "\n  mutation CreateProject($input: ProjectCreateInput!) {\n    projectCreate(input: $input) {\n      success\n      project {\n        id\n        name\n        state\n        teams {\n          nodes { id key name }\n        }\n      }\n    }\n  }\n";
 export declare const UPDATE_PROJECT_MUTATION = "\n  mutation UpdateProject($id: String!, $input: ProjectUpdateInput!) {\n    projectUpdate(id: $id, input: $input) {\n      success\n      project {\n        id\n        name\n        teams {\n          nodes {\n            id\n            key\n            name\n          }\n        }\n      }\n    }\n  }\n";
+export declare const ARCHIVE_PROJECT_MUTATION = "\n  mutation ArchiveProject($id: String!) {\n    projectArchive(id: $id) {\n      success\n      lastSyncId\n      entity {\n        id\n      }\n    }\n  }\n";
+export declare const DELETE_PROJECT_MUTATION = "\n  mutation DeleteProject($id: String!) {\n    projectDelete(id: $id) {\n      success\n      lastSyncId\n      entity {\n        id\n      }\n    }\n  }\n";

package/dist/queries/projects.js

@@ -102,3 +102,25 @@ export const UPDATE_PROJECT_MUTATION = `
     }
   }
 `;
+export const ARCHIVE_PROJECT_MUTATION = `
+  mutation ArchiveProject($id: String!) {
+    projectArchive(id: $id) {
+      success
+      lastSyncId
+      entity {
+        id
+      }
+    }
+  }
+`;
+export const DELETE_PROJECT_MUTATION = `
+  mutation DeleteProject($id: String!) {
+    projectDelete(id: $id) {
+      success
+      lastSyncId
+      entity {
+        id
+      }
+    }
+  }
+`;

package/dist/queries/releases-types.d.ts

@@ -0,0 +1,85 @@
+/**
+ * Typed response shapes for the queries in `./releases.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+interface ReleaseStageRef {
+    id: string;
+    name: string;
+    type: string;
+    color: string | null;
+}
+interface ReleasePipelineRef {
+    id: string;
+    name: string;
+}
+interface ReleaseDocumentRef {
+    id: string;
+    title: string;
+    slugId: string;
+}
+/** Mirrors the release selection set used by `GET_RELEASES_QUERY`. */
+export interface ReleaseListNode {
+    id: string;
+    name: string;
+    description: string | null;
+    version: string | null;
+    url: string | null;
+    startDate: string | null;
+    targetDate: string | null;
+    startedAt: string | null;
+    completedAt: string | null;
+    canceledAt: string | null;
+    stage: ReleaseStageRef | null;
+    pipeline: ReleasePipelineRef | null;
+    createdAt: string;
+    updatedAt: string;
+}
+/** Mirrors `GET_RELEASE_BY_ID_QUERY` — adds `documents`. */
+export interface ReleaseDetailNode extends ReleaseListNode {
+    documents: {
+        nodes: ReleaseDocumentRef[];
+    };
+}
+/**
+ * Mirrors the release selection set on `CREATE_RELEASE_MUTATION` —
+ * a subset of `ReleaseListNode` (no startDate/targetDate/lifecycle
+ * timestamps; no documents).
+ */
+export interface CreatedReleaseNode {
+    id: string;
+    name: string;
+    description: string | null;
+    version: string | null;
+    url: string | null;
+    stage: ReleaseStageRef | null;
+    pipeline: ReleasePipelineRef | null;
+    createdAt: string;
+    updatedAt: string;
+}
+interface ReleasePipelineNode {
+    id: string;
+    name: string;
+    stages: {
+        nodes: ReleaseStageRef[];
+    };
+}
+export interface GetReleasesResponse {
+    releases: {
+        nodes: ReleaseListNode[];
+    };
+}
+export interface GetReleaseByIdResponse {
+    release: ReleaseDetailNode | null;
+}
+export interface CreateReleaseResponse {
+    releaseCreate: {
+        success: boolean;
+        release: CreatedReleaseNode | null;
+    };
+}
+export interface GetReleasePipelinesResponse {
+    releasePipelines: {
+        nodes: ReleasePipelineNode[];
+    };
+}
+export {};

package/dist/queries/releases-types.js

@@ -0,0 +1,5 @@
+/**
+ * Typed response shapes for the queries in `./releases.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+export {};