Few incremental improvements

Author: MrRefactoring

src/version2/issueSearch.ts

@@ -468,8 +468,8 @@ export class IssueSearch {
    * Searches for issues using [JQL](https://confluence.atlassian.com/x/egORLQ). Recent updates might not be immediately
    * visible in the returned search results.
    *
-   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/) consistency,
-   * you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
+   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/)
+   * consistency, you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
    *
    * If the JQL query expression is too large to be encoded as a query parameter, use the
    * [POST](#searchforissuesusingjqlenhancedsearchpost) version of this resource.
@@ -492,8 +492,8 @@ export class IssueSearch {
    * Searches for issues using [JQL](https://confluence.atlassian.com/x/egORLQ). Recent updates might not be immediately
    * visible in the returned search results.
    *
-   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/) consistency,
-   * you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
+   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/)
+   * consistency, you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
    *
    * If the JQL query expression is too large to be encoded as a query parameter, use the
    * [POST](#searchforissuesusingjqlenhancedsearchpost) version of this resource.
@@ -538,11 +538,11 @@ export class IssueSearch {
   /**
    * Searches for issues using [JQL](https://confluence.atlassian.com/x/egORLQ).
    *
-   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/) consistency,
-   * you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
+   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/)
+   * consistency, you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
    *
-   * There is a [GET](#searchforissuesusingjqlenhancedsearch) version of this resource that can be used for smaller JQL query
-   * expressions.
+   * There is a [GET](#searchforissuesusingjqlenhancedsearch) version of this resource that can be used for smaller JQL
+   * query expressions.
    *
    * This operation can be accessed anonymously.
    *
@@ -561,11 +561,11 @@ export class IssueSearch {
   /**
    * Searches for issues using [JQL](https://confluence.atlassian.com/x/egORLQ).
    *
-   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/) consistency,
-   * you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
+   * If you need [read-after-write](https://developer.atlassian.com/cloud/jira/platform/search-and-reconcile/)
+   * consistency, you can utilize the `reconcileIssues` parameter to ensure stronger consistency assurances.
    *
-   * There is a [GET](#searchforissuesusingjqlenhancedsearch) version of this resource that can be used for smaller JQL query
-   * expressions.
+   * There is a [GET](#searchforissuesusingjqlenhancedsearch) version of this resource that can be used for smaller JQL
+   * query expressions.
    *
    * This operation can be accessed anonymously.
    *

src/version2/jiraExpressions.ts

@@ -343,9 +343,9 @@ export class JiraExpressions {
   /**
    * Evaluates a Jira expression and returns its value. The difference between this and `eval` is that this endpoint
    * uses the enhanced search API when evaluating JQL queries. This API is eventually consistent, unlike the strongly
-   * consistent `eval` API. This allows for better performance and scalability. In addition, this API's response for
-   * JQL evaluation is based on a scrolling view (backed by a `nextPageToken`) instead of a paginated view
-   * (backed by `startAt` and `totalCount`).
+   * consistent `eval` API. This allows for better performance and scalability. In addition, this API's response for JQL
+   * evaluation is based on a scrolling view (backed by a `nextPageToken`) instead of a paginated view (backed by
+   * `startAt` and `totalCount`).
    *
    * This resource can be used to test Jira expressions that you plan to use elsewhere, or to fetch data in a flexible
    * way. Consult the [Jira expressions
@@ -382,8 +382,8 @@ export class JiraExpressions {
    *   The current customer request. Available only when the customer request is provided in the request context
    *   object.
    *
-   * In addition, you can pass custom context variables along with their types. You can then access them from
-   * the Jira expression by key. You can use the following variables in a custom context:
+   * In addition, you can pass custom context variables along with their types. You can then access them from the Jira
+   * expression by key. You can use the following variables in a custom context:
    *
    * - `user`: A [user](https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference#user)
    *   specified as an Atlassian account ID.
@@ -406,9 +406,9 @@ export class JiraExpressions {
   /**
    * Evaluates a Jira expression and returns its value. The difference between this and `eval` is that this endpoint
    * uses the enhanced search API when evaluating JQL queries. This API is eventually consistent, unlike the strongly
-   * consistent `eval` API. This allows for better performance and scalability. In addition, this API's response for
-   * JQL evaluation is based on a scrolling view (backed by a `nextPageToken`) instead of a paginated view
-   * (backed by `startAt` and `totalCount`).
+   * consistent `eval` API. This allows for better performance and scalability. In addition, this API's response for JQL
+   * evaluation is based on a scrolling view (backed by a `nextPageToken`) instead of a paginated view (backed by
+   * `startAt` and `totalCount`).
    *
    * This resource can be used to test Jira expressions that you plan to use elsewhere, or to fetch data in a flexible
    * way. Consult the [Jira expressions
@@ -445,8 +445,8 @@ export class JiraExpressions {
    *   The current customer request. Available only when the customer request is provided in the request context
    *   object.
    *
-   * In addition, you can pass custom context variables along with their types. You can then access them from
-   * the Jira expression by key. You can use the following variables in a custom context:
+   * In addition, you can pass custom context variables along with their types. You can then access them from the Jira
+   * expression by key. You can use the following variables in a custom context:
    *
    * - `user`: A [user](https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference#user)
    *   specified as an Atlassian account ID.

src/version3/models/index.ts

@@ -1,4 +1,3 @@
-export * from './jiraExpressionEvaluateRequest';
 export * from './updateDefaultProjectClassification';
 export * from './workflowUpdateRequest';
 export * from './mappingsByIssueTypeOverride';

src/version3/models/jExpEvaluateMetaData.ts

@@ -3,13 +3,13 @@ import { JiraExpressionsComplexity } from './jiraExpressionsComplexity';
 
 export interface JExpEvaluateMetaData {
   /**
-   * Contains information about the expression complexity. For example, the number of steps it took to
-   * evaluate the expression.
+   * Contains information about the expression complexity. For example, the number of steps it took to evaluate the
+   * expression.
    */
   complexity?: JiraExpressionsComplexity;
   /**
-   * Contains information about the `issues` variable in the context. For example, is the issues were loaded
-   * with JQL, information about the page will be included here.
+   * Contains information about the `issues` variable in the context. For example, is the issues were loaded with JQL,
+   * information about the page will be included here.
    */
   issues?: JExpEvaluateIssuesMeta;
 }

src/version3/models/jiraExpressionEvaluateRequest.ts

@@ -1,86 +1 @@
-export interface SearchAndReconsileIssuesUsingJql {
-  /**
-   * A [JQL](https://confluence.atlassian.com/x/egORLQ) expression. For performance reasons, this field requires a
-   * bounded query. A bounded query is a query with a search restriction.
-   *
-   * Example of an unbounded query: `order by key desc`. Example of a bounded query: `assignee = currentUser() order by
-   * key`.
-   */
-  jql?: string;
-  /**
-   * The token for a page to fetch that is not the first page. The first page has a `nextPageToken` of `null`. Use the
-   * `nextPageToken` to fetch the next page of issues.
-   */
-  nextPageToken?: string;
-  /**
-   * The maximum number of items to return. Depending on search criteria, real number of items returned may be smaller.
-   * It returns max 5000 issues.
-   */
-  maxResults?: number;
-  /**
-   * A list of fields to return for each issue, use it to retrieve a subset of fields. This parameter accepts a
-   * comma-separated list. Expand options include:
-   *
-   * - `*all` Returns all fields.
-   * - `*navigable` Returns navigable fields.
-   * - `id` Returns only issue IDs.
-   * - Any issue field, prefixed with a minus to exclude.
-   *
-   *   The default is `id`.
-   *
-   *   Examples:
-   * - `summary,comment` Returns only the summary and comments fields only.
-   * - `-description` Returns all navigable (default) fields except description.
-   * - `*all,-comment` Returns all fields except comments.
-   *
-   *   Multiple `fields` parameters can be included in a request.
-   *
-   *   Note: By default, this resource returns IDs only. This differs from [GET
-   *   issue](#api-rest-api-3-issue-issueIdOrKey-get) where the default is all fields.
-   */
-  fields?: ('*all' | '*navigable' | 'id' | `-${string}` | string)[] | '*all' | '*navigable' | 'id' | string;
-  /**
-   * Use [expand](https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#expansion) to include additional
-   * information about issues in the response. Note that, unlike the majority of instances where `expand` is specified,
-   * `expand` is defined as a list of values. The expand options are:
-   *
-   * - `renderedFields` Returns field values rendered in HTML format.
-   * - `names` Returns the display name of each field.
-   * - `schema` Returns the schema describing a field type.
-   * - `transitions` Returns all possible transitions for the issue.
-   * - `operations` Returns all possible operations for the issue.
-   * - `editmeta` Returns information about how each field can be edited.
-   * - `changelog` Returns a list of recent updates to an issue, sorted by date, starting from the most recent.
-   * - `versionedRepresentations` Instead of `fields`, returns `versionedRepresentations` a JSON array containing each
-   *   version of a field's value, with the highest numbered item representing the most recent version.
-   */
-  expand?:
-    | 'renderedFields'
-    | 'names'
-    | 'schema'
-    | 'transitions'
-    | 'operations'
-    | 'editmeta'
-    | 'changelog'
-    | 'versionedRepresentations'
-    | string
-    | (
-        | 'renderedFields'
-        | 'names'
-        | 'schema'
-        | 'transitions'
-        | 'operations'
-        | 'editmeta'
-        | 'changelog'
-        | 'versionedRepresentations'
-        | string
-      )[];
-  /** A list of up to 5 issue properties to include in the results. This parameter accepts a comma-separated list. */
-  properties?: string[];
-  /** Reference fields by their key (rather than ID). The default is `false`. */
-  fieldsByKeys?: boolean;
-  /** Fail this request early if we can't retrieve all field data. */
-  failFast?: boolean;
-  /** Strong consistency issue ids to be reconciled with search results. Accepts max 50 ids. All issues must exist. */
-  reconcileIssues?: number[];
-}
+