@api-client/core 0.19.9 → 0.19.11

package/data/apis/schema-api/schemas/person.json

@@ -1,104 +0,0 @@
-{
-  "$id": "http://example.com/example.json",
-  "type": "object",
-  "definitions": {},
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "properties": {
-    "id": {
-      "$id": "/properties/id",
-      "type": "string",
-      "title": "The Id Schema ",
-      "default": "",
-      "examples": [
-        "R34fg663H9KW9MMSKISI"
-      ]
-    },
-    "name": {
-      "$id": "/properties/name",
-      "type": "string",
-      "title": "The Name Schema ",
-      "default": "",
-      "examples": [
-        "Pawel Psztyc"
-      ]
-    },
-    "birthday": {
-      "$id": "/properties/birthday",
-      "type": "string",
-      "title": "The Birthday Schema ",
-      "default": "",
-      "examples": [
-        "1983-10-20"
-      ]
-    },
-    "gender": {
-      "$id": "/properties/gender",
-      "type": "string",
-      "title": "The Gender Schema ",
-      "default": "",
-      "examples": [
-        "male"
-      ]
-    },
-    "url": {
-      "$id": "/properties/url",
-      "type": "string",
-      "title": "The Url Schema ",
-      "default": "",
-      "examples": [
-        "https://domain.com/profile/pawel.psztyc"
-      ]
-    },
-    "image": {
-      "$id": "/properties/image",
-      "type": "object",
-      "properties": {
-        "url": {
-          "$id": "/properties/image/properties/url",
-          "type": "string",
-          "title": "The Url Schema ",
-          "default": "",
-          "examples": [
-            "https://domain.com/profile/pawel.psztyc/image"
-          ]
-        },
-        "thumb": {
-          "$id": "/properties/image/properties/thumb",
-          "type": "string",
-          "title": "The Thumb Schema ",
-          "default": "",
-          "examples": [
-            "https://domain.com/profile/pawel.psztyc/image/thumb"
-          ]
-        }
-      }
-    },
-    "tagline": {
-      "$id": "/properties/tagline",
-      "type": "string",
-      "title": "The Tagline Schema ",
-      "default": "",
-      "examples": [
-        "Some text about me."
-      ]
-    },
-    "language": {
-      "$id": "/properties/language",
-      "type": "string",
-      "title": "The Language Schema ",
-      "default": "",
-      "examples": [
-        "en_GB"
-      ]
-    },
-    "etag": {
-      "$id": "/properties/etag",
-      "type": "string",
-      "title": "The Etag Schema ",
-      "default": "",
-      "examples": [
-        "W\\244m4n5kj3gbn2nj4k4n4"
-      ]
-    }
-  }
-}

package/data/apis/schema-api/schemas/person.xsd

@@ -1,26 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
-  <xs:element name="resource">
-    <xs:complexType>
-      <xs:sequence>
-        <xs:element name="id" type="xs:string"></xs:element>
-        <xs:element name="name" type="xs:string"></xs:element>
-        <xs:element name="birthday" type="xs:date"></xs:element>
-        <xs:element name="gender" type="xs:string"></xs:element>
-        <xs:element name="url" type="xs:string"></xs:element>
-        <xs:element name="image">
-          <xs:complexType>
-            <xs:sequence>
-              <xs:element name="url" type="xs:string"></xs:element>
-              <xs:element name="thumb" type="xs:string"></xs:element>
-            </xs:sequence>
-          </xs:complexType>
-        </xs:element>
-        <xs:element name="tagline" type="xs:string"></xs:element>
-        <xs:element name="language" type="xs:string"></xs:element>
-      </xs:sequence>
-      <xs:attribute name="error" type="xs:boolean" use="required"></xs:attribute>
-      <xs:attribute name="type" type="xs:string" use="required"></xs:attribute>
-    </xs:complexType>
-  </xs:element>
-</xs:schema>

package/data/apis/schema-api/types/DemoPerson.raml

@@ -1,67 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Person
-description: |
-  A person but without examples defined inline.
-
-type: object
-
-properties:
-  id:
-    xml:
-      attribute: true
-    description: A unique identifier for a person. It is a 32 bit string containing alphanumeric characters.
-    type: string
-    example: ad3fd6d4-af89-11eb-8529-0242ac130003
-  name:
-    required: true
-    example: John Smith
-    description: Person full name. The input will be rejected if this property is not set while creating new object.
-    type: string
-    pattern: "[0-9a-zA-Z ]+"
-    xml:
-      attribute: true
-      name: fullname
-  birthday:
-    type: date-only
-    description: The person's date of birth, represented as YYYY-MM-DD.
-    examples:
-      Example 1: 1983-10-20
-      Example 2: 1994-08-29
-  gender?:
-    type: string
-    description: |
-      The person's gender. Possible values includes, but are not limited to, the following values:
-      * "male" - Male gender.
-      * "female" - Female gender.
-      * "other" - Other.
-    example: male
-  url:
-    type: string
-    description: The URL of this person's profile.
-  image: 
-    type: !include ../resourceTypes/image.raml
-    xml:
-      wrapped: true
-  tagline:
-    type: string
-    description: The brief description (tagline) of this person.
-  language:
-    type: string
-    description: The user's preferred language for rendering.
-    example: "Polish"
-  tags:
-    description: Tags added to the person.
-    type: array
-    items: 
-      properties:
-        name: 
-          type: string
-          description: The name of the tag
-          example: Manager
-        id:
-          type: string
-          description: Tag's identifier.
-          example: ad3fda8a-af89-11eb-8529-0242ac130003
-      xml:
-        wrapped: false

package/data/apis/secured-api/oauth-2-custom-settings.raml

@@ -1,143 +0,0 @@
-#%RAML 1.0 AnnotationTypeDeclaration
-displayName: OAuth 2.0 custom settings
-description: |
-  OAuth 2.0 allows to extend the specification with custom access token types,
-  endpoint parameters, grant types or response types.
-  This annotation allows you to annotate the `settings` property of OAuth 2.0
-  security scheme type to inform applications about additional settings.
-  ## Use case
-  Let's say a authorization server requires to send a `resource` query parameter
-  with the authorization request. The `resource` parameter can be any string.
-  Currently it is impossible to define this property in RAML file.
-  Similar if the code exchange request requires to put the `resource` parameter
-  into the request body.
-  This annotation allows you to define this parameter with the RAML definition
-  and place the parameter in the right request.
-  ## Annotation Target
-  The [annotation target](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#annotation-targets)
-  for those annotations is `SecuritySchemeSettings`.
-  You can only apply it to Security Scheme `settings` property.
-  ## Example
-  ```yaml
-  annotationTypes:
-    customSettings: !include oauth-2-custom-settings.raml
-  securitySchemes:
-    oauth2:
-      type: OAuth 2.0
-      describedBy:
-        headers:
-          Authorization:
-            example: "Bearer token"
-      settings:
-        (customSettings):
-          authorizationGrants: [custom_grant]
-          ignoreDefaultGrants:
-          authorizationSettings:
-            queryParameters:
-              resource:
-                type: string
-                required: true
-                description: |
-                  A resource ID that defines a domain of authorization.
-            headers:
-              x-auth-resource:
-                type: string
-                required: false
-          accessTokenSettings:
-            body:
-              resource:
-                type: string
-                required: true
-                description: |
-                  A resource ID that defines a domain of authorization.
-        accessTokenUri: https://auth.domain.com/authorize
-        authorizationUri: https://auth.domain.com/token
-        authorizationGrants: [implicit]
-        scopes: profile
-  ```
-  ## API console
-  This annotation is recognized and respected by API console.
-allowedTargets: [ SecuritySchemeSettings ]
-properties:
-  authorizationSettings:
-    description: |
-      Settings to be applied to the `authorizationUri` GET request.
-      Define any query parameters or headers that are required by your OAuth 2.0
-      authorization server implementation.
-      This settings can be applied only to `token` and `code` requests
-    type: object
-    displayName: Authorization settings
-    required: false
-    properties:
-      queryParameters:
-        displayName: Authorization query parameters
-        description: |
-          Query parameters to be applied to the `authorizationUri`.
-          Use the same notation as RAML's `queryParameters`.
-          If you define a parameter that is already defined in OAuth 2.0 specification
-          (RFC6749) it should be ignored by the processor.
-        type: object
-        required: false
-        properties:
-          /a-zA-Z0-9\-\_/*:
-            type: object
-            required: false
-  accessTokenSettings:
-    displayName: Access token settings
-    description: |
-      Settings to be applied to the token endpoint POST request.
-      Define query parameters, headers or custom body paramaeters that should
-      be included into the request.
-      Note, as per RFC6749, the request content type is `application/x-www-form-urlencoded`
-      and the processor has to always assume this content type.
-    type: object
-    required: false
-    properties:
-      queryParameters:
-        displayName: Token query parameters
-        description: |
-          Query parameters to be applied to the `accessTokenUri`.
-          Use the same notation as RAML's `queryParameters`.
-          OAuth 2.0 specification does not specify any query parameters for this
-          type of request.
-        type: object
-        required: false
-        properties:
-          /a-zA-Z0-9\-\_/*:
-            type: object
-            required: false
-      headers:
-        displayName: Token request headers
-        description: |
-          Headers to be set on the token request.
-          Use the same notation as RAML's `headers`.
-        type: object
-        required: false
-        properties:
-          /a-zA-Z0-9\-\_/*:
-            type: object
-            required: false
-      body:
-        displayName: Token body parameters
-        description: |
-          Body parameters to be applied to the `accessTokenUri`.
-          Properties will be applied to the default set of OAuth 2.0 token request
-          parameters.
-          If you define a parameter that is already defined in OAuth 2.0 specification
-          (RFC6749) it should be ignored by the processor.
-        type: object
-        required: false
-  authorizationGrants:
-    type: string[]
-    displayName: Custom authorization grants
-    required: false
-    description: |
-      List of custom authorization granst supported by your OAuth 2.0 server
-  ignoreDefaultGrants:
-    type: nil
-    required: false
-    description: |
-      If set, the processor should not use any of the `authorizationGrants`
-      properties defined in the `settings` and should be replaced by
-      `authorizationGrants` defined in this annotation.
-      This can be used only if this annotation `authorizationGrants` is set.

package/data/apis/secured-api/oauth2-header-delivery.raml

@@ -1,13 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 2.0
-displayName: Token delivery described as header parameter only
-settings:
-  accessTokenUri: https://header.com/token
-  authorizationUri: https://header.com/auth
-  authorizationGrants: password
-  scopes: [header]
-describedBy:
-  headers:
-    token:
-      type: string
-      description: Apply access token as a header here.

package/data/apis/secured-api/oauth2-no-delivery.raml

@@ -1,8 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 2.0
-displayName: Token delivery described as query parameter only
-settings:
-  accessTokenUri: https://token.com
-  authorizationUri: https://auth.com
-  authorizationGrants: authorization_code
-  scopes: [profile, email]

package/data/apis/secured-api/oauth2-no-grants.raml

@@ -1,12 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 2.0
-displayName: This OAuth2 has no auth grants!
-settings:
-  accessTokenUri: https://token.com
-  authorizationUri: https://auth.com
-  scopes: [profile, email]
-describedBy:
-  queryParameters:
-    access_token:
-      type: string
-      description: Apply access token here.

package/data/apis/secured-api/oauth2-pkce.raml

@@ -1,13 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 2.0
-displayName: This OAuth2 has PKCE annotation
-settings:
-  (pkce): true
-  accessTokenUri: https://token.com
-  authorizationUri: https://auth.com
-  scopes: [profile, email]
-describedBy:
-  queryParameters:
-    access_token:
-      type: string
-      description: Apply access token here.

package/data/apis/secured-api/oauth2-query-delivery.raml

@@ -1,13 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 2.0
-displayName: Token delivery described as query parameter only
-settings:
-  accessTokenUri: https://query.com/token
-  authorizationUri: https://query.com/auth
-  authorizationGrants: client_credentials
-  scopes: [query]
-describedBy:
-  queryParameters:
-    access_token:
-      type: string
-      description: Apply access token as a query here.

package/data/apis/secured-api/oauth_1_0.raml

@@ -1,8 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 1.0
-description: OAuth 1.0 continues to be supported for all API requests, but OAuth 2.0 is now preferred.
-settings:
-  requestTokenUri: http://api.domain.com/oauth1/request_token
-  authorizationUri: http://api.domain.com/oauth1/authorize
-  tokenCredentialsUri: http://api.domain.com/oauth1/access_token
-  signatures: [RSA-SHA1, HMAC-SHA1]

package/data/apis/secured-api/oauth_1_0_no-settings.raml

@@ -1,3 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 1.0
-description: This has no settings.

package/data/apis/secured-api/oauth_1_0_no-signature.raml

@@ -1,7 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 1.0
-description: OAuth 1.0 continues to be supported for all API requests, but OAuth 2.0 is now preferred.
-settings:
-  requestTokenUri: http://api.domain.com/oauth1/request_token
-  authorizationUri: http://api.domain.com/oauth1/authorize
-  tokenCredentialsUri: http://api.domain.com/oauth1/access_token

package/data/apis/secured-api/oauth_1_0_signature.raml

@@ -1,8 +0,0 @@
-#%RAML 1.0 SecurityScheme
-type: OAuth 1.0
-description: OAuth 1.0 continues to be supported for all API requests, but OAuth 2.0 is now preferred.
-settings:
-  requestTokenUri: http://api.domain.com/oauth1/request_token
-  authorizationUri: http://api.domain.com/oauth1/authorize
-  tokenCredentialsUri: http://api.domain.com/oauth1/access_token
-  signatures: [RSA-SHA1]

package/data/apis/secured-api/passthrough-querystring.raml

@@ -1,16 +0,0 @@
-#%RAML 1.0 SecurityScheme
-
-description: |
-  This API supports Pass Through Authentication.
-type: Pass Through
-describedBy:
-  queryString:
-    type: object
-    properties:
-      queryStringProperty1:
-        type: number
-        required: true
-      queryStringProperty2:
-        description: Random string
-        type: string
-        required: false

package/data/apis/secured-api/passthrough.raml

@@ -1,24 +0,0 @@
-#%RAML 1.0 SecurityScheme
-
-description: |
-  This API supports Pass Through Authentication.
-type: Pass Through
-describedBy:
-  queryParameters:
-    query:
-      type: string
-      example: my-value
-      description: |
-        This demonstrates how Pass Through authentication
-        works with `api-authorization-method` component.
-    debugTokenParam:
-      description: Select one of available values to run the request in the debug mode with selected level.
-      enum: [Info, Log, Warning, Error, Critical]
-      type: string
-      required: false
-  headers:
-    api_key:
-      type: string
-      pattern: "[0-9a-zA-Z\\.-]+"
-      description: |
-        This headers has pattern included in the definition.