@gitkraken/core-gitlens 0.5.116 → 0.7.0

package/dist/git/models/issue.d.ts

@@ -1,7 +1,8 @@
-import type { RequireSome, RequireSomeWithProps } from '../../utils/types.js';
-import type { IssueOrPullRequest, IssueOrPullRequestState } from './issueOrPullRequest.js';
-import type { ProviderReference } from './remoteProvider.js';
-import type { RepositoryIdentityDescriptor } from './repositoryIdentities.js';
+import { RequireSome, RequireSomeWithProps } from "../../utils/types.js";
+import { RepositoryIdentityDescriptor } from "./repositoryIdentities.js";
+import { ProviderReference } from "./remoteProvider.js";
+import { IssueOrPullRequest, IssueOrPullRequestState } from "./issueOrPullRequest.js";
+//#region ../git/src/models/issue.d.ts
 /** Selects which issue states a read should include. `all` covers open + closed. */
 export type IssueStateFilter = 'open' | 'closed' | 'all';
 /**
@@ -10,17 +11,17 @@ export type IssueStateFilter = 'open' | 'closed' | 'all';
  * The last two are USER-INDEPENDENT — they describe the issue, not the caller — and neither is a SCOPE: either
  * one alone matches every such issue on the host, so a search using one still needs a repository/org scope.
  */
-export type IssueSearchRelationship = 
+export type IssueSearchRelationship =
 /** Authored by the current user. */
-'authored'
+'authored' |
 /** Assigned to the current user. */
- | 'assigned'
+'assigned' |
 /** Mentions the current user. */
- | 'mentioned'
+'mentioned' |
 /** Assigned to ANYONE. Excludes unassigned issues — see {@link IssueSearchCriteria.relationships}. */
- | 'any-assignee'
+'any-assignee' |
 /** Assigned to nobody. The complement of `any-assignee`, not a broadening of it. */
- | 'unassigned';
+'unassigned';
 /**
  * A field an issue read can be ordered by, provider-neutral. No provider expresses all of them: each read
  * validates the requested key against the capability its provider declares and refuses one it can't express
@@ -31,25 +32,25 @@ export type IssueSearchRelationship =
  * has no close date at all — it models the equivalent as `resolutiondate`. Collapsing them would force one of
  * those two providers to lie about which date it ordered by.
  */
-export type IssueSortField = 
+export type IssueSortField =
 /** Creation date. */
-'created'
+'created' |
 /** Last activity. */
- | 'updated'
+'updated' |
 /** Close date. Only where the provider orders by it server-side — notably NOT GitHub. */
- | 'closed'
+'closed' |
 /** Resolution date (Jira `resolutiondate`, Azure `ResolvedDate`). Distinct from `closed`. */
- | 'resolved'
+'resolved' |
 /** Number of comments. */
- | 'comments'
+'comments' |
 /** Reactions/upvotes. */
- | 'reactions'
+'reactions' |
 /** The provider's own priority field. */
- | 'priority'
+'priority' |
 /** Due date. */
- | 'dueDate'
+'dueDate' |
 /** Alphabetical by title. */
- | 'title';
+'title';
 /**
  * How an issue read is ordered, as `field:direction` — the same shape `BranchSorting`/`TagSorting` already use,
  * so it is one serializable string a consumer can persist, compare, or bind straight to a setting or a dropdown.
@@ -85,48 +86,48 @@ export declare const defaultIssueSort: IssueSorting;
  * describing a different result set than the paging that came with them.
  */
 export interface IssueSearchCriteria {
-    /**
-     * Relationships to constrain on, OR-ed together (each becomes its own provider query, unioned and deduped).
-     * Omitted means NO relationship constraint at all — every issue in scope, assigned or not — which requires a
-     * repository/org scope.
-     *
-     * `any-assignee` and `unassigned` partition the scope between them and are mutually exclusive; passing both is
-     * refused rather than silently dropping one. Note that "all visible issues" is the OMITTED case, NOT
-     * `any-assignee`, which excludes unassigned issues.
-     */
-    relationships?: IssueSearchRelationship[];
-    /**
-     * Free text, matched by the provider's own relevance rules — NOT a substring match, and not a way to smuggle
-     * qualifiers: a token that would read as one is dropped, as are quotes and control characters, so text can
-     * never re-scope the search. The structured criteria are the qualifier channel.
-     */
-    text?: string;
-    /** Issue states to include. Omitted reads open issues only. */
-    state?: IssueStateFilter;
-    /** Labels the issue must carry — AND-ed, matching GitHub's own `label:` semantics. */
-    labels?: string[];
-    milestone?: string;
-    /** ISO date (`YYYY-MM-DD`). The most effective narrowing criterion by far on a large scope. */
-    updatedAfter?: string;
-    /** ISO date (`YYYY-MM-DD`). */
-    createdAfter?: string;
-    /** Issues with no linked pull request. */
-    withoutLinkedPullRequest?: boolean;
-    /** Includes issues in archived repositories, which are excluded by default. */
-    includeArchived?: boolean;
-    /**
-     * How to order the results. Omitted means `updated:desc`, which is what this search has always served.
-     *
-     * Validated like every other criterion — all-or-nothing against {@link IssueSearchCapabilities.sorts}: a key
-     * the provider can't express server-side refuses the WHOLE read rather than falling back to the default.
-     * Serving another order is not a smaller error than serving a wider result: combined with the provider's
-     * result ceiling it returns a different subset than was asked for, and the paging that comes with it describes
-     * that other subset.
-     *
-     * Do not change it mid-pagination. A cursor carries the sort it was produced under, and threading it under a
-     * different key is refused rather than serving a sequence with gaps and repeats: drop the cursor instead.
-     */
-    sort?: IssueSorting;
+  /**
+   * Relationships to constrain on, OR-ed together (each becomes its own provider query, unioned and deduped).
+   * Omitted means NO relationship constraint at all — every issue in scope, assigned or not — which requires a
+   * repository/org scope.
+   *
+   * `any-assignee` and `unassigned` partition the scope between them and are mutually exclusive; passing both is
+   * refused rather than silently dropping one. Note that "all visible issues" is the OMITTED case, NOT
+   * `any-assignee`, which excludes unassigned issues.
+   */
+  relationships?: IssueSearchRelationship[];
+  /**
+   * Free text, matched by the provider's own relevance rules — NOT a substring match, and not a way to smuggle
+   * qualifiers: a token that would read as one is dropped, as are quotes and control characters, so text can
+   * never re-scope the search. The structured criteria are the qualifier channel.
+   */
+  text?: string;
+  /** Issue states to include. Omitted reads open issues only. */
+  state?: IssueStateFilter;
+  /** Labels the issue must carry — AND-ed, matching GitHub's own `label:` semantics. */
+  labels?: string[];
+  milestone?: string;
+  /** ISO date (`YYYY-MM-DD`). The most effective narrowing criterion by far on a large scope. */
+  updatedAfter?: string;
+  /** ISO date (`YYYY-MM-DD`). */
+  createdAfter?: string;
+  /** Issues with no linked pull request. */
+  withoutLinkedPullRequest?: boolean;
+  /** Includes issues in archived repositories, which are excluded by default. */
+  includeArchived?: boolean;
+  /**
+   * How to order the results. Omitted means `updated:desc`, which is what this search has always served.
+   *
+   * Validated like every other criterion — all-or-nothing against {@link IssueSearchCapabilities.sorts}: a key
+   * the provider can't express server-side refuses the WHOLE read rather than falling back to the default.
+   * Serving another order is not a smaller error than serving a wider result: combined with the provider's
+   * result ceiling it returns a different subset than was asked for, and the paging that comes with it describes
+   * that other subset.
+   *
+   * Do not change it mid-pagination. A cursor carries the sort it was produced under, and threading it under a
+   * different key is refused rather than serving a sequence with gaps and repeats: drop the cursor instead.
+   */
+  sort?: IssueSorting;
 }
 /**
  * Which {@link IssueSearchCriteria} fields a provider's filtered issue search can express server-side.
@@ -135,98 +136,131 @@ export interface IssueSearchCriteria {
  * refused outright, so a consumer should offer neither the surface nor its chips.
  */
 export interface IssueSearchCapabilities {
-    /** Relationships the search can constrain on. Empty means the search itself is unsupported. */
-    relationships: IssueSearchRelationship[];
-    text: boolean;
-    labels: boolean;
-    milestone: boolean;
-    updatedAfter: boolean;
-    createdAfter: boolean;
-    withoutLinkedPullRequest: boolean;
-    /** Whether {@link IssueSearchCriteria.state} can select anything other than the provider's default (open). */
-    states: boolean;
-    /**
-     * Sort keys the search can express IN SERVER. Always contains at least `updated:desc` — the historical default
-     * — when the search exists at all, so it is never empty for a usable surface; a provider without a filtered
-     * search reports an empty `relationships`, which is already the signal that there is no surface to order.
-     */
-    sorts: IssueSorting[];
+  /** Relationships the search can constrain on. Empty means the search itself is unsupported. */
+  relationships: IssueSearchRelationship[];
+  text: boolean;
+  labels: boolean;
+  milestone: boolean;
+  updatedAfter: boolean;
+  createdAfter: boolean;
+  withoutLinkedPullRequest: boolean;
+  /** Whether {@link IssueSearchCriteria.state} can select anything other than the provider's default (open). */
+  states: boolean;
+  /**
+   * Sort keys the search can express IN SERVER. Always contains at least `updated:desc` — the historical default
+   * — when the search exists at all, so it is never empty for a usable surface; a provider without a filtered
+   * search reports an empty `relationships`, which is already the signal that there is no surface to order.
+   */
+  sorts: IssueSorting[];
 }
 export interface IssueShape extends IssueOrPullRequest {
-    /** `undefined` when the provider can't resolve the author, e.g. a deleted GitHub account */
-    author: IssueMember | undefined;
-    assignees: IssueMember[];
-    repository?: IssueRepository;
-    labels?: IssueLabel[];
-    body?: string;
-    project?: IssueProject;
-    issueType?: string;
+  /** `undefined` when the provider can't resolve the author, e.g. a deleted GitHub account */
+  author: IssueMember | undefined;
+  assignees: IssueMember[];
+  /** The provider's own workflow state, when it exposes one beyond the normalized open/closed state. */
+  providerState?: IssueProviderState;
+  repository?: IssueRepository;
+  labels?: IssueLabel[];
+  body?: string;
+  /** The syntax used by `body`. When omitted, consumers should treat `body` as Markdown. */
+  bodyFormat?: IssueBodyFormat;
+  project?: IssueProject;
+  issueType?: string;
+  /** An issue can belong to several Jira sprints; Azure reports one iteration. */
+  iterations?: IssueIteration[];
 }
 export declare class Issue implements IssueShape {
-    readonly provider: ProviderReference;
-    readonly id: string;
-    readonly nodeId: string | undefined;
-    readonly title: string;
-    readonly url: string;
-    readonly createdDate: Date;
-    readonly updatedDate: Date;
-    readonly closed: boolean;
-    readonly state: IssueOrPullRequestState;
-    readonly author: IssueMember | undefined;
-    readonly assignees: IssueMember[];
-    readonly repository?: IssueRepository | undefined;
-    readonly closedDate?: Date | undefined;
-    readonly labels?: IssueLabel[] | undefined;
-    readonly commentsCount?: number | undefined;
-    readonly thumbsUpCount?: number | undefined;
-    readonly body?: string | undefined;
-    readonly project?: IssueProject | undefined;
-    readonly number?: string | undefined;
-    readonly issueType?: string | undefined;
-    readonly type = "issue";
-    constructor(provider: ProviderReference, id: string, nodeId: string | undefined, title: string, url: string, createdDate: Date, updatedDate: Date, closed: boolean, state: IssueOrPullRequestState, author: IssueMember | undefined, assignees: IssueMember[], repository?: IssueRepository | undefined, closedDate?: Date | undefined, labels?: IssueLabel[] | undefined, commentsCount?: number | undefined, thumbsUpCount?: number | undefined, body?: string | undefined, project?: IssueProject | undefined, number?: string | undefined, issueType?: string | undefined);
-    static is(issue: unknown): issue is Issue;
+  readonly provider: ProviderReference;
+  readonly id: string;
+  readonly nodeId: string | undefined;
+  readonly title: string;
+  readonly url: string;
+  readonly createdDate: Date;
+  readonly updatedDate: Date;
+  readonly closed: boolean;
+  readonly state: IssueOrPullRequestState;
+  readonly author: IssueMember | undefined;
+  readonly assignees: IssueMember[];
+  readonly repository?: IssueRepository | undefined;
+  readonly closedDate?: Date | undefined;
+  readonly labels?: IssueLabel[] | undefined;
+  readonly commentsCount?: number | undefined;
+  readonly thumbsUpCount?: number | undefined;
+  readonly body?: string | undefined;
+  readonly project?: IssueProject | undefined;
+  readonly number?: string | undefined;
+  readonly issueType?: string | undefined;
+  readonly providerState?: IssueProviderState | undefined;
+  readonly bodyFormat?: IssueBodyFormat | undefined;
+  readonly iterations?: IssueIteration[] | undefined;
+  readonly type = "issue";
+  constructor(provider: ProviderReference, id: string, nodeId: string | undefined, title: string, url: string, createdDate: Date, updatedDate: Date, closed: boolean, state: IssueOrPullRequestState, author: IssueMember | undefined, assignees: IssueMember[], repository?: IssueRepository | undefined, closedDate?: Date | undefined, labels?: IssueLabel[] | undefined, commentsCount?: number | undefined, thumbsUpCount?: number | undefined, body?: string | undefined, project?: IssueProject | undefined, number?: string | undefined, issueType?: string | undefined, providerState?: IssueProviderState | undefined, bodyFormat?: IssueBodyFormat | undefined, iterations?: IssueIteration[] | undefined);
+  static is(issue: unknown): issue is Issue;
 }
+export type IssueBodyFormat = 'markdown' | 'jira-wiki';
 export declare const enum RepositoryAccessLevel {
-    Admin = 100,
-    Maintain = 40,
-    Write = 30,
-    Triage = 20,
-    Read = 10,
-    None = 0
+  Admin = 100,
+  Maintain = 40,
+  Write = 30,
+  Triage = 20,
+  Read = 10,
+  None = 0
 }
 export interface IssueLabel {
-    color?: string;
-    name: string;
+  color?: string;
+  name: string;
+}
+/**
+ * Sprint metadata is optional because some providers only report an iteration path. An absent `isActive`
+ * means unknown, not inactive, so consumers must not use it to exclude those iterations by default.
+ */
+export interface IssueIteration {
+  /**
+   * A sprint id on Jira, the verbatim iteration path on Azure — so it is only meaningful within the provider's
+   * project, never across providers. Unique at read time but NOT durable: Azure rewrites the path when an
+   * iteration node is renamed or re-parented, so don't persist it as a long-lived id.
+   */
+  id: string;
+  name: string;
+  isActive?: boolean;
+  startDate?: Date;
+  endDate?: Date;
 }
 export interface IssueMember {
-    id: string;
-    /**
-     * Absent when the provider exposes no display name for the member. Optional on purpose: a fallback string
-     * invented here (`'unknown'`, `''`) can't be told apart from a real name downstream, so it can't be undone by a
-     * consumer that needs to render something else — or nothing at all, as when the member feeds an AI prompt.
-     * Each consumer picks its own presentation.
-     */
-    name?: string;
-    /** The provider's handle for this person, when it has one — GitHub's login, Azure's `uniqueName` (a UPN,
-     *  so an email), Bitbucket's mutable `nickname`. Display/labelling only: it is neither guaranteed present
-     *  (GitLab's native mapper has none) nor a stable identity, so never key a match off it. */
-    username?: string;
-    avatarUrl?: string;
-    url?: string;
+  id: string;
+  /**
+   * Absent when the provider exposes no display name for the member. Optional on purpose: a fallback string
+   * invented here (`'unknown'`, `''`) can't be told apart from a real name downstream, so it can't be undone by a
+   * consumer that needs to render something else — or nothing at all, as when the member feeds an AI prompt.
+   * Each consumer picks its own presentation.
+   */
+  name?: string;
+  /** The provider's handle for this person, when it has one — GitHub's login, Azure's `uniqueName` (a UPN,
+   *  so an email), Bitbucket's mutable `nickname`. Display/labelling only: it is neither guaranteed present
+   *  (GitLab's native mapper has none) nor a stable identity, so never key a match off it. */
+  username?: string;
+  avatarUrl?: string;
+  url?: string;
 }
+export type IssueProviderState = {
+  id?: string;
+  name: string;
+  color?: string;
+  category?: 'TO_DO' | 'IN_PROGRESS' | 'DONE';
+};
 export interface IssueProject {
-    id: string;
-    name: string;
-    resourceId: string;
-    resourceName: string;
+  id: string;
+  name: string;
+  resourceId: string;
+  resourceName: string;
 }
 export interface IssueRepository {
-    owner: string;
-    repo: string;
-    accessLevel?: RepositoryAccessLevel;
-    url?: string;
-    id?: string;
+  owner: string;
+  repo: string;
+  accessLevel?: RepositoryAccessLevel;
+  url?: string;
+  id?: string;
 }
 export type IssueRepositoryIdentityDescriptor = RequireSomeWithProps<RequireSome<RepositoryIdentityDescriptor<string>, 'provider'>, 'provider', 'id' | 'domain' | 'repoDomain' | 'repoName'> & RequireSomeWithProps<RequireSome<RepositoryIdentityDescriptor<string>, 'remote'>, 'remote', 'domain'>;
+//#endregion
 //# sourceMappingURL=issue.d.ts.map

package/dist/git/models/issue.js

@@ -1,87 +1,89 @@
-var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
-    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
-    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
-    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
-    return c > 3 && r && Object.defineProperty(target, key, r), r;
-};
-var Issue_1;
-import { loggable } from '../../utils/decorators/log.js';
+import { loggable } from "../../utils/decorators/log.js";
+import __decorate from "../../_virtual/@oxc-project+runtime/helpers/esm/decorate.js";
+//#region ../git/src/models/issue.ts
+var _Issue;
 /**
- * The order every issue read that HAS a default applies when the caller asks for none: most recently updated
- * first, which is what those reads served before ordering was an option.
- *
- * One definition rather than one per layer, because it is a promise made in several places at once — the criteria
- * model documents it, the GitHub query emits it, and the result-ceiling warning quotes it — and three copies would
- * be free to disagree about what "the default" is.
- *
- * Note it is not a default every read has, and the two layers differ. The API client's account-wide "my issues"
- * search (`GitHubApi.searchMyIssues`) never requested an order, so a direct caller omitting `sort` still gets
- * GitHub's relevance order — the default is opt-in there, to keep that read's already-shipped results unchanged.
- * The FACADE does apply it: GitHub declares `updated:desc` among its account-wide keys, so
- * `readAccountWideIssuesPage` resolves the omission to this default and forwards it, and that read's emitted query
- * gained a `sort:updated` qualifier it did not have before. A read whose surface cannot express even this key is
- * the only one the facade leaves in the provider's own order.
- */
-export const defaultIssueSort = 'updated:desc';
-let Issue = Issue_1 = class Issue {
-    provider;
-    id;
-    nodeId;
-    title;
-    url;
-    createdDate;
-    updatedDate;
-    closed;
-    state;
-    author;
-    assignees;
-    repository;
-    closedDate;
-    labels;
-    commentsCount;
-    thumbsUpCount;
-    body;
-    project;
-    number;
-    issueType;
-    type = 'issue';
-    constructor(provider, id, nodeId, title, url, createdDate, updatedDate, closed, state, author, assignees, repository, closedDate, labels, commentsCount, thumbsUpCount, body, project, number, issueType) {
-        this.provider = provider;
-        this.id = id;
-        this.nodeId = nodeId;
-        this.title = title;
-        this.url = url;
-        this.createdDate = createdDate;
-        this.updatedDate = updatedDate;
-        this.closed = closed;
-        this.state = state;
-        this.author = author;
-        this.assignees = assignees;
-        this.repository = repository;
-        this.closedDate = closedDate;
-        this.labels = labels;
-        this.commentsCount = commentsCount;
-        this.thumbsUpCount = thumbsUpCount;
-        this.body = body;
-        this.project = project;
-        this.number = number;
-        this.issueType = issueType;
-    }
-    static is(issue) {
-        return issue instanceof Issue_1;
-    }
+* The order every issue read that HAS a default applies when the caller asks for none: most recently updated
+* first, which is what those reads served before ordering was an option.
+*
+* One definition rather than one per layer, because it is a promise made in several places at once — the criteria
+* model documents it, the GitHub query emits it, and the result-ceiling warning quotes it — and three copies would
+* be free to disagree about what "the default" is.
+*
+* Note it is not a default every read has, and the two layers differ. The API client's account-wide "my issues"
+* search (`GitHubApi.searchMyIssues`) never requested an order, so a direct caller omitting `sort` still gets
+* GitHub's relevance order — the default is opt-in there, to keep that read's already-shipped results unchanged.
+* The FACADE does apply it: GitHub declares `updated:desc` among its account-wide keys, so
+* `readAccountWideIssuesPage` resolves the omission to this default and forwards it, and that read's emitted query
+* gained a `sort:updated` qualifier it did not have before. A read whose surface cannot express even this key is
+* the only one the facade leaves in the provider's own order.
+*/
+const defaultIssueSort = "updated:desc";
+let Issue = _Issue = class Issue {
+	provider;
+	id;
+	nodeId;
+	title;
+	url;
+	createdDate;
+	updatedDate;
+	closed;
+	state;
+	author;
+	assignees;
+	repository;
+	closedDate;
+	labels;
+	commentsCount;
+	thumbsUpCount;
+	body;
+	project;
+	number;
+	issueType;
+	providerState;
+	bodyFormat;
+	iterations;
+	type = "issue";
+	constructor(provider, id, nodeId, title, url, createdDate, updatedDate, closed, state, author, assignees, repository, closedDate, labels, commentsCount, thumbsUpCount, body, project, number, issueType, providerState, bodyFormat, iterations) {
+		this.provider = provider;
+		this.id = id;
+		this.nodeId = nodeId;
+		this.title = title;
+		this.url = url;
+		this.createdDate = createdDate;
+		this.updatedDate = updatedDate;
+		this.closed = closed;
+		this.state = state;
+		this.author = author;
+		this.assignees = assignees;
+		this.repository = repository;
+		this.closedDate = closedDate;
+		this.labels = labels;
+		this.commentsCount = commentsCount;
+		this.thumbsUpCount = thumbsUpCount;
+		this.body = body;
+		this.project = project;
+		this.number = number;
+		this.issueType = issueType;
+		this.providerState = providerState;
+		this.bodyFormat = bodyFormat;
+		this.iterations = iterations;
+	}
+	static is(issue) {
+		return issue instanceof _Issue;
+	}
 };
-Issue = Issue_1 = __decorate([
-    loggable(i => i.id)
-], Issue);
-export { Issue };
-export var RepositoryAccessLevel;
-(function (RepositoryAccessLevel) {
-    RepositoryAccessLevel[RepositoryAccessLevel["Admin"] = 100] = "Admin";
-    RepositoryAccessLevel[RepositoryAccessLevel["Maintain"] = 40] = "Maintain";
-    RepositoryAccessLevel[RepositoryAccessLevel["Write"] = 30] = "Write";
-    RepositoryAccessLevel[RepositoryAccessLevel["Triage"] = 20] = "Triage";
-    RepositoryAccessLevel[RepositoryAccessLevel["Read"] = 10] = "Read";
-    RepositoryAccessLevel[RepositoryAccessLevel["None"] = 0] = "None";
-})(RepositoryAccessLevel || (RepositoryAccessLevel = {}));
+Issue = _Issue = __decorate([loggable((i) => i.id)], Issue);
+let RepositoryAccessLevel = /* @__PURE__ */ function(RepositoryAccessLevel) {
+	RepositoryAccessLevel[RepositoryAccessLevel["Admin"] = 100] = "Admin";
+	RepositoryAccessLevel[RepositoryAccessLevel["Maintain"] = 40] = "Maintain";
+	RepositoryAccessLevel[RepositoryAccessLevel["Write"] = 30] = "Write";
+	RepositoryAccessLevel[RepositoryAccessLevel["Triage"] = 20] = "Triage";
+	RepositoryAccessLevel[RepositoryAccessLevel["Read"] = 10] = "Read";
+	RepositoryAccessLevel[RepositoryAccessLevel["None"] = 0] = "None";
+	return RepositoryAccessLevel;
+}({});
+//#endregion
+export { Issue, RepositoryAccessLevel, defaultIssueSort };
+
 //# sourceMappingURL=issue.js.map

package/dist/git/models/issue.js.map

@@ -1 +1 @@
-{"version":3,"file":"issue.js","sourceRoot":"","sources":["../../../src/git/models/issue.ts"],"names":[],"mappings":";;;;;;;AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,kCAAkC,CAAC;AA+D5D;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAiB,cAAc,CAAC;AAgGtD,IAAM,KAAK,aAAX,MAAM,KAAK;IAIA,QAAQ;IACR,EAAE;IACF,MAAM;IACN,KAAK;IACL,GAAG;IACH,WAAW;IACX,WAAW;IACX,MAAM;IACN,KAAK;IACL,MAAM;IACN,SAAS;IACT,UAAU;IACV,UAAU;IACV,MAAM;IACN,aAAa;IACb,aAAa;IACb,IAAI;IACJ,OAAO;IACP,MAAM;IACN,SAAS;IAtBjB,IAAI,GAAG,OAAO,CAAC;IAExB,YACiB,QAA2B,EAC3B,EAAU,EACV,MAA0B,EAC1B,KAAa,EACb,GAAW,EACX,WAAiB,EACjB,WAAiB,EACjB,MAAe,EACf,KAA8B,EAC9B,MAA+B,EAC/B,SAAwB,EACxB,UAA4B,EAC5B,UAAiB,EACjB,MAAqB,EACrB,aAAsB,EACtB,aAAsB,EACtB,IAAa,EACb,OAAsB,EACtB,MAAe,EACf,SAAkB;wBAnBlB,QAAQ;kBACR,EAAE;sBACF,MAAM;qBACN,KAAK;mBACL,GAAG;2BACH,WAAW;2BACX,WAAW;sBACX,MAAM;qBACN,KAAK;sBACL,MAAM;yBACN,SAAS;0BACT,UAAU;0BACV,UAAU;sBACV,MAAM;6BACN,aAAa;6BACb,aAAa;oBACb,IAAI;uBACJ,OAAO;sBACP,MAAM;yBACN,SAAS;IACvB,CAAC;IAEG,AAAP,MAAM,CAAC,EAAE,CAAC,KAAc;QACvB,OAAO,KAAK,mBAAiB,CAAC;IAC/B,CAAC;CACD,CAAA;AA7BY,KAAK;IADjB,QAAQ,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;GACP,KAAK,CA6BjB;;AAED,MAAM,CAAN,IAAkB,qBAOjB;AAPD,WAAkB,qBAAqB;IACtC,qEAAW,CAAA;IACX,0EAAa,CAAA;IACb,oEAAU,CAAA;IACV,sEAAW,CAAA;IACX,kEAAS,CAAA;IACT,iEAAQ,CAAA;AACT,CAAC,EAPiB,qBAAqB,KAArB,qBAAqB,QAOtC"}
+{"version":3,"file":"issue.js","names":[],"sources":["../../../../git/src/models/issue.ts"],"sourcesContent":["import { loggable } from '@gitlens/utils/decorators/log.js';\nimport type { RequireSome, RequireSomeWithProps } from '@gitlens/utils/types.js';\nimport type { IssueOrPullRequest, IssueOrPullRequestState } from './issueOrPullRequest.js';\nimport type { ProviderReference } from './remoteProvider.js';\nimport type { RepositoryIdentityDescriptor } from './repositoryIdentities.js';\n\n/** Selects which issue states a read should include. `all` covers open + closed. */\nexport type IssueStateFilter = 'open' | 'closed' | 'all';\n\n/**\n * One relationship a filtered issue search can constrain on.\n *\n * The last two are USER-INDEPENDENT — they describe the issue, not the caller — and neither is a SCOPE: either\n * one alone matches every such issue on the host, so a search using one still needs a repository/org scope.\n */\nexport type IssueSearchRelationship =\n\t/** Authored by the current user. */\n\t| 'authored'\n\t/** Assigned to the current user. */\n\t| 'assigned'\n\t/** Mentions the current user. */\n\t| 'mentioned'\n\t/** Assigned to ANYONE. Excludes unassigned issues — see {@link IssueSearchCriteria.relationships}. */\n\t| 'any-assignee'\n\t/** Assigned to nobody. The complement of `any-assignee`, not a broadening of it. */\n\t| 'unassigned';\n\n/**\n * A field an issue read can be ordered by, provider-neutral. No provider expresses all of them: each read\n * validates the requested key against the capability its provider declares and refuses one it can't express\n * server-side, rather than serving a differently-ordered list under the name of the one that was asked for.\n *\n * `closed` and `resolved` are deliberately SEPARATE, not two names for the same date. Azure DevOps tracks both\n * and they differ (an issue can be closed without being resolved and resolved without being closed), and Jira\n * has no close date at all — it models the equivalent as `resolutiondate`. Collapsing them would force one of\n * those two providers to lie about which date it ordered by.\n */\nexport type IssueSortField =\n\t/** Creation date. */\n\t| 'created'\n\t/** Last activity. */\n\t| 'updated'\n\t/** Close date. Only where the provider orders by it server-side — notably NOT GitHub. */\n\t| 'closed'\n\t/** Resolution date (Jira `resolutiondate`, Azure `ResolvedDate`). Distinct from `closed`. */\n\t| 'resolved'\n\t/** Number of comments. */\n\t| 'comments'\n\t/** Reactions/upvotes. */\n\t| 'reactions'\n\t/** The provider's own priority field. */\n\t| 'priority'\n\t/** Due date. */\n\t| 'dueDate'\n\t/** Alphabetical by title. */\n\t| 'title';\n\n/**\n * How an issue read is ordered, as `field:direction` — the same shape `BranchSorting`/`TagSorting` already use,\n * so it is one serializable string a consumer can persist, compare, or bind straight to a setting or a dropdown.\n */\nexport type IssueSorting = `${IssueSortField}:asc` | `${IssueSortField}:desc`;\n\n/**\n * The order every issue read that HAS a default applies when the caller asks for none: most recently updated\n * first, which is what those reads served before ordering was an option.\n *\n * One definition rather than one per layer, because it is a promise made in several places at once — the criteria\n * model documents it, the GitHub query emits it, and the result-ceiling warning quotes it — and three copies would\n * be free to disagree about what \"the default\" is.\n *\n * Note it is not a default every read has, and the two layers differ. The API client's account-wide \"my issues\"\n * search (`GitHubApi.searchMyIssues`) never requested an order, so a direct caller omitting `sort` still gets\n * GitHub's relevance order — the default is opt-in there, to keep that read's already-shipped results unchanged.\n * The FACADE does apply it: GitHub declares `updated:desc` among its account-wide keys, so\n * `readAccountWideIssuesPage` resolves the omission to this default and forwards it, and that read's emitted query\n * gained a `sort:updated` qualifier it did not have before. A read whose surface cannot express even this key is\n * the only one the facade leaves in the provider's own order.\n */\nexport const defaultIssueSort: IssueSorting = 'updated:desc';\n\n/**\n * What a filtered issue search narrows on: a provider-neutral criteria set, translated to each provider's own\n * query language by its integration.\n *\n * Structured rather than a provider query string so a consumer can render filter chips and hide the ones a\n * provider can't express, and so the same criteria mean the same thing on a provider whose query language looks\n * nothing like GitHub's search syntax. Every field is validated against the provider's declared capability\n * BEFORE the read runs, all-or-nothing: a criterion the provider can't express server-side refuses the whole\n * read rather than serving a list that was never narrowed. Client-side narrowing is not an option — the dropped\n * items still counted toward the page and cursor the provider produced, so a post-filter would leave the items\n * describing a different result set than the paging that came with them.\n */\nexport interface IssueSearchCriteria {\n\t/**\n\t * Relationships to constrain on, OR-ed together (each becomes its own provider query, unioned and deduped).\n\t * Omitted means NO relationship constraint at all — every issue in scope, assigned or not — which requires a\n\t * repository/org scope.\n\t *\n\t * `any-assignee` and `unassigned` partition the scope between them and are mutually exclusive; passing both is\n\t * refused rather than silently dropping one. Note that \"all visible issues\" is the OMITTED case, NOT\n\t * `any-assignee`, which excludes unassigned issues.\n\t */\n\trelationships?: IssueSearchRelationship[];\n\t/**\n\t * Free text, matched by the provider's own relevance rules — NOT a substring match, and not a way to smuggle\n\t * qualifiers: a token that would read as one is dropped, as are quotes and control characters, so text can\n\t * never re-scope the search. The structured criteria are the qualifier channel.\n\t */\n\ttext?: string;\n\t/** Issue states to include. Omitted reads open issues only. */\n\tstate?: IssueStateFilter;\n\t/** Labels the issue must carry — AND-ed, matching GitHub's own `label:` semantics. */\n\tlabels?: string[];\n\tmilestone?: string;\n\t/** ISO date (`YYYY-MM-DD`). The most effective narrowing criterion by far on a large scope. */\n\tupdatedAfter?: string;\n\t/** ISO date (`YYYY-MM-DD`). */\n\tcreatedAfter?: string;\n\t/** Issues with no linked pull request. */\n\twithoutLinkedPullRequest?: boolean;\n\t/** Includes issues in archived repositories, which are excluded by default. */\n\tincludeArchived?: boolean;\n\t/**\n\t * How to order the results. Omitted means `updated:desc`, which is what this search has always served.\n\t *\n\t * Validated like every other criterion — all-or-nothing against {@link IssueSearchCapabilities.sorts}: a key\n\t * the provider can't express server-side refuses the WHOLE read rather than falling back to the default.\n\t * Serving another order is not a smaller error than serving a wider result: combined with the provider's\n\t * result ceiling it returns a different subset than was asked for, and the paging that comes with it describes\n\t * that other subset.\n\t *\n\t * Do not change it mid-pagination. A cursor carries the sort it was produced under, and threading it under a\n\t * different key is refused rather than serving a sequence with gaps and repeats: drop the cursor instead.\n\t */\n\tsort?: IssueSorting;\n}\n\n/**\n * Which {@link IssueSearchCriteria} fields a provider's filtered issue search can express server-side.\n *\n * An empty `relationships` with every flag false means the provider has NO filtered issue search — the read is\n * refused outright, so a consumer should offer neither the surface nor its chips.\n */\nexport interface IssueSearchCapabilities {\n\t/** Relationships the search can constrain on. Empty means the search itself is unsupported. */\n\trelationships: IssueSearchRelationship[];\n\ttext: boolean;\n\tlabels: boolean;\n\tmilestone: boolean;\n\tupdatedAfter: boolean;\n\tcreatedAfter: boolean;\n\twithoutLinkedPullRequest: boolean;\n\t/** Whether {@link IssueSearchCriteria.state} can select anything other than the provider's default (open). */\n\tstates: boolean;\n\t/**\n\t * Sort keys the search can express IN SERVER. Always contains at least `updated:desc` — the historical default\n\t * — when the search exists at all, so it is never empty for a usable surface; a provider without a filtered\n\t * search reports an empty `relationships`, which is already the signal that there is no surface to order.\n\t */\n\tsorts: IssueSorting[];\n}\n\nexport interface IssueShape extends IssueOrPullRequest {\n\t/** `undefined` when the provider can't resolve the author, e.g. a deleted GitHub account */\n\tauthor: IssueMember | undefined;\n\tassignees: IssueMember[];\n\t/** The provider's own workflow state, when it exposes one beyond the normalized open/closed state. */\n\tproviderState?: IssueProviderState;\n\trepository?: IssueRepository;\n\tlabels?: IssueLabel[];\n\tbody?: string;\n\t/** The syntax used by `body`. When omitted, consumers should treat `body` as Markdown. */\n\tbodyFormat?: IssueBodyFormat;\n\tproject?: IssueProject;\n\tissueType?: string;\n\t/** An issue can belong to several Jira sprints; Azure reports one iteration. */\n\titerations?: IssueIteration[];\n}\n\n@loggable(i => i.id)\nexport class Issue implements IssueShape {\n\treadonly type = 'issue';\n\n\tconstructor(\n\t\tpublic readonly provider: ProviderReference,\n\t\tpublic readonly id: string,\n\t\tpublic readonly nodeId: string | undefined,\n\t\tpublic readonly title: string,\n\t\tpublic readonly url: string,\n\t\tpublic readonly createdDate: Date,\n\t\tpublic readonly updatedDate: Date,\n\t\tpublic readonly closed: boolean,\n\t\tpublic readonly state: IssueOrPullRequestState,\n\t\tpublic readonly author: IssueMember | undefined,\n\t\tpublic readonly assignees: IssueMember[],\n\t\tpublic readonly repository?: IssueRepository,\n\t\tpublic readonly closedDate?: Date,\n\t\tpublic readonly labels?: IssueLabel[],\n\t\tpublic readonly commentsCount?: number,\n\t\tpublic readonly thumbsUpCount?: number,\n\t\tpublic readonly body?: string,\n\t\tpublic readonly project?: IssueProject,\n\t\tpublic readonly number?: string,\n\t\tpublic readonly issueType?: string,\n\t\tpublic readonly providerState?: IssueProviderState,\n\t\tpublic readonly bodyFormat?: IssueBodyFormat,\n\t\tpublic readonly iterations?: IssueIteration[],\n\t) {}\n\n\tstatic is(issue: unknown): issue is Issue {\n\t\treturn issue instanceof Issue;\n\t}\n}\n\nexport type IssueBodyFormat = 'markdown' | 'jira-wiki';\n\nexport const enum RepositoryAccessLevel {\n\tAdmin = 100,\n\tMaintain = 40,\n\tWrite = 30,\n\tTriage = 20,\n\tRead = 10,\n\tNone = 0,\n}\n\nexport interface IssueLabel {\n\tcolor?: string;\n\tname: string;\n}\n\n/**\n * Sprint metadata is optional because some providers only report an iteration path. An absent `isActive`\n * means unknown, not inactive, so consumers must not use it to exclude those iterations by default.\n */\nexport interface IssueIteration {\n\t/**\n\t * A sprint id on Jira, the verbatim iteration path on Azure — so it is only meaningful within the provider's\n\t * project, never across providers. Unique at read time but NOT durable: Azure rewrites the path when an\n\t * iteration node is renamed or re-parented, so don't persist it as a long-lived id.\n\t */\n\tid: string;\n\tname: string;\n\tisActive?: boolean;\n\tstartDate?: Date;\n\tendDate?: Date;\n}\n\nexport interface IssueMember {\n\tid: string;\n\t/**\n\t * Absent when the provider exposes no display name for the member. Optional on purpose: a fallback string\n\t * invented here (`'unknown'`, `''`) can't be told apart from a real name downstream, so it can't be undone by a\n\t * consumer that needs to render something else — or nothing at all, as when the member feeds an AI prompt.\n\t * Each consumer picks its own presentation.\n\t */\n\tname?: string;\n\t/** The provider's handle for this person, when it has one — GitHub's login, Azure's `uniqueName` (a UPN,\n\t *  so an email), Bitbucket's mutable `nickname`. Display/labelling only: it is neither guaranteed present\n\t *  (GitLab's native mapper has none) nor a stable identity, so never key a match off it. */\n\tusername?: string;\n\tavatarUrl?: string;\n\turl?: string;\n}\n\nexport type IssueProviderState = {\n\tid?: string;\n\tname: string;\n\tcolor?: string;\n\tcategory?: 'TO_DO' | 'IN_PROGRESS' | 'DONE';\n};\n\nexport interface IssueProject {\n\tid: string;\n\tname: string;\n\tresourceId: string;\n\tresourceName: string;\n}\n\nexport interface IssueRepository {\n\towner: string;\n\trepo: string;\n\taccessLevel?: RepositoryAccessLevel;\n\turl?: string;\n\tid?: string;\n}\n\nexport type IssueRepositoryIdentityDescriptor = RequireSomeWithProps<\n\tRequireSome<RepositoryIdentityDescriptor<string>, 'provider'>,\n\t'provider',\n\t'id' | 'domain' | 'repoDomain' | 'repoName'\n> &\n\tRequireSomeWithProps<RequireSome<RepositoryIdentityDescriptor<string>, 'remote'>, 'remote', 'domain'>;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AA+EA,MAAa,mBAAiC;AAsGvC,IAAM,QAAA,SAAN,MAAM,MAA4B;CAIvB;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CAzBjB,OAAgB;CAEhB,YACC,UACA,IACA,QACA,OACA,KACA,aACA,aACA,QACA,OACA,QACA,WACA,YACA,YACA,QACA,eACA,eACA,MACA,SACA,QACA,WACA,eACA,YACA,YACC;EAvBe,KAAA,WAAA;EACA,KAAA,KAAA;EACA,KAAA,SAAA;EACA,KAAA,QAAA;EACA,KAAA,MAAA;EACA,KAAA,cAAA;EACA,KAAA,cAAA;EACA,KAAA,SAAA;EACA,KAAA,QAAA;EACA,KAAA,SAAA;EACA,KAAA,YAAA;EACA,KAAA,aAAA;EACA,KAAA,aAAA;EACA,KAAA,SAAA;EACA,KAAA,gBAAA;EACA,KAAA,gBAAA;EACA,KAAA,OAAA;EACA,KAAA,UAAA;EACA,KAAA,SAAA;EACA,KAAA,YAAA;EACA,KAAA,gBAAA;EACA,KAAA,aAAA;EACA,KAAA,aAAA;CACd;CAEH,OAAO,GAAG,OAAgC;EACzC,OAAO,iBAAA;CACR;AACD;AAjCC,QAAA,SAAA,WAAA,CAAA,UAAS,MAAK,EAAE,EAAE,CAAA,GAAA,KAAA;AAqCnB,IAAkB,wBAAX,yBAAA,uBAAA;CACN,sBAAA,sBAAA,WAAA,OAAA;CACA,sBAAA,sBAAA,cAAA,MAAA;CACA,sBAAA,sBAAA,WAAA,MAAA;CACA,sBAAA,sBAAA,YAAA,MAAA;CACA,sBAAA,sBAAA,UAAA,MAAA;CACA,sBAAA,sBAAA,UAAA,KAAA;;AACD,EAAA,CAAA,CAAA"}

package/dist/git/models/issueOrPullRequest.d.ts

@@ -1,19 +1,21 @@
-import type { ProviderReference } from './remoteProvider.js';
+import { ProviderReference } from "./remoteProvider.js";
+//#region ../git/src/models/issueOrPullRequest.d.ts
 export interface IssueOrPullRequest {
-    readonly type: IssueOrPullRequestType;
-    readonly provider: ProviderReference;
-    readonly id: string;
-    readonly nodeId: string | undefined;
-    readonly title: string;
-    readonly url: string;
-    readonly createdDate: Date;
-    readonly updatedDate: Date;
-    readonly closedDate?: Date;
-    readonly closed: boolean;
-    readonly state: IssueOrPullRequestState;
-    readonly commentsCount?: number;
-    readonly thumbsUpCount?: number;
+  readonly type: IssueOrPullRequestType;
+  readonly provider: ProviderReference;
+  readonly id: string;
+  readonly nodeId: string | undefined;
+  readonly title: string;
+  readonly url: string;
+  readonly createdDate: Date;
+  readonly updatedDate: Date;
+  readonly closedDate?: Date;
+  readonly closed: boolean;
+  readonly state: IssueOrPullRequestState;
+  readonly commentsCount?: number;
+  readonly thumbsUpCount?: number;
 }
 export type IssueOrPullRequestType = 'issue' | 'pullrequest';
 export type IssueOrPullRequestState = 'opened' | 'closed' | 'merged';
+//#endregion
 //# sourceMappingURL=issueOrPullRequest.d.ts.map

package/dist/git/models/issueOrPullRequest.js

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=issueOrPullRequest.js.map