@api-client/ui 0.2.0 → 0.2.3

package/demo/apis/SE-10469/SE-10469.raml

@@ -1,11 +0,0 @@
-#%RAML 1.0
-version: v1
-title: Purina-Supplier-PurchaseOrder
-# types:
-#   purchaseOrder: !include Purchase-Order-oagis-id-dd32f9c6c01048a19e15c423c9c741ae.json
-
-/purina/b2b/supplier/purchaseOrder:
-  post:
-    body:
-      application/json:
-        type: !include Purchase-Order-oagis-id-dd32f9c6c01048a19e15c423c9c741ae.json

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-address.raml

@@ -1,126 +0,0 @@
-#%RAML 1.0 DataType
-
-uses:
-  lib: ../libraries/library-context-and-preference.raml
-  base-lib: ../libraries/library-base.raml
-
-displayName: Address
-description: Used to express the values of a US address, but can also be used for non-US addresses
-
-type: [lib.preferable, lib.contextual, base-lib.base]
-additionalProperties: false
-
-properties:
-  line1:
-    displayName: Address Line 1
-    required: false
-    type: string
-    minLength: 0
-    maxLength: 64
-    description: The street name part of the address
-    example: 156 Trentini Ave
-  line2:
-    displayName: Address Line 2
-    required: false
-    type: string
-    minLength: 0
-    maxLength: 64
-    description: The additional street name part of the address
-    example: Suite 101
-  line3:
-    displayName: Address Line 3
-    required: false
-    type: string
-    minLength: 0
-    maxLength: 64
-    description: For Attn to a specific person in an organization
-    example: "Attn: John Doe"
-  line4:
-    displayName: Address Line 4
-    required: false
-    type: string
-    minLength: 0
-    maxLength: 64
-    description: Any additional information that does not fit the above three lines can be inserted here
-  city:
-    displayName: City
-    required: false
-    type: string
-    description: The city name part of the address
-    example: Atlanta
-  county:
-    displayName: County
-    required: false
-    type: string
-    description: Rarely used county name within a US state
-    example: Fulton
-  state-region-code:
-    displayName: State or Region Code
-    description: In countries such as the USA which has states, this field holds the code of the state.  Otherwise, it holds the code of a region or province
-    required: false
-    type: string
-    examples:
-      state-example: GA
-      region-example: MBR
-  state-region-name:
-    displayName: State or Region Name
-    description: In countries such as the USA which has states, this field holds the full name of the state.  Otherwise, it holds the full name of a region or province
-    required: false
-    type: string
-    examples:
-      state-example: Georgia
-      region-example: Marmara Bolgesi
-  country:
-    displayName: Country
-    description: The name of the country. It can be abbreviated or full.
-    required: false
-    type: string
-    example: U.S.A.
-  postal-code:
-    displayName: Primary Postal Code
-    required: false
-    type: string
-    description: Most country addresses use a primary postal code.  In the U.S. the primary postal code is the first 5 digits of the zip code.
-    example: "12345" 
-  additional-postal-code:
-    displayName: Additional Postal Code
-    required: false
-    type: string
-    description: In some countries which use a primary postal may also include an additional postal code.  In the U.S. the additional postal code is the last 4 digits of the 9 digit full postal code.  Most people only know their primary postal code.  However, post offices can use these additional postal codes to increase efficiencies and reduce costs.
-    example: "1234" 
-  validity:
-    displayName: Address Validity
-    required: false
-    enum:
-      - Unknown
-      - Valid
-      - Invalid
-    description:  |
-      An address can be validated against a service to confirm its existence and its format.  This field shows either the address has been validated or not, and if validated what the result is.
-      Unknown: We do not know if the address has been validated or not
-      Valid:  The address has been validated and the result came back as a valid address
-      Invalid: The validation process returned a negative result and the address is NOT valid, meaning it either does not exist or is not formatted correctly and it should not be used until fixed.
-examples:
-  us-address-example:
-    context: home
-    line1: 3388 Hamilton St
-    line2: Apt 1
-    city: Philadelphia
-    state-region-code: PA
-    state-region-name: Pennsylvania
-    country: USA
-    postal-code: "19104"
-    additional-postal-code: "0388"
-    validity: Valid
-    preference-index: 3
-  canada-address-example:
-    context: office
-    line1: 2701 Riverside Dr
-    line2: Suite No813
-    city: Ottowa
-    state-region-code: ON
-    country: Canada
-    postal-code: "K1A 0B1"
-    additional-postal-code: "0388"
-    validity: Valid
-    preference-index: 3

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-base.raml

@@ -1,31 +0,0 @@
-#%RAML 1.0 DataType
-
-uses:
-  prop-lib: ../libraries/library-property.raml
-
-displayName: Base DataType
-description: Base data type is used as the super type of most business data types.  Base has properties that all business entities commonly have.
-
-type: object
-additionalProperties: false
-
-properties:
-  additional-properties:
-    displayName: Additional Properties
-    description: When a data type is defined for various reasons it may be missing some properties.  This array of property objects keeps track of the missed properties
-    required: false
-    type: prop-lib.properties
-
-example:
-  additional-properties:
-    - order: 1
-      name: forgotten-property
-      value: value
-      type: string
-    - name: forgotten-number-array
-      is-array: true
-      delimiter:  ","
-      value: 1,3,4,5,6
-      type: integer
-
-    

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-basic-questions-set.raml

@@ -1,42 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Basic Question Set
-description: Basic question set contains 6 questions (what, when, where, who, why and how) that are asked for any event to gather information about the event.
-
-properties: 
-  what:
-    displayName: What
-    description:  answers what has happened
-    required: false
-    type: string
-    example: Created
-  when:
-    displayName: When
-    description:  answers when it has happened.  Always in Zulu(GMT) time in ISO 8601 format yyyy-MM-ddThh:mm:ss.sssZ
-    required: false
-    type: datetime
-    example: 2018-09-12T15:10:19.123Z
-  where:
-    displayName: Where
-    description:  answers where it has happened.  Usually location or locations
-    required: false
-    type: string
-    example: \\pcnsdnca02a\folder1
-  who:
-    displayName: Who
-    description:  answers who has done it.  Usually name or names
-    required: false
-    type: string
-    example: AFLHQ\e99999
-  why:
-    displayName: Why
-    description:  answers why it has been done.  Usually reason or reasons
-    required: false
-    type: string
-    example: new file
-  how:
-    displayName: How
-    description:  answers how it has been done.  Usually mean or means
-    required: false
-    type: string
-    example: Microsoft Word

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-code-description.raml

@@ -1,36 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Code Description
-description: Used to explain the meaning of a code, with short and long descriptions
-
-type: object
-additionalProperties: true
-
-properties: 
-  context:
-    required: false
-    type: string
-    displayName: Context
-    description: a name that represents to whom the code belongs such as the name of a system or software component or under which context it has been created such as an error condition.  Use kebab-case for multi words.
-    example: experienceAPI-for-datacap-claim-app
-  code:
-    required: false
-    type: string
-    displayName: Code
-    description: a code that represent a specific condition
-  short-description:
-    required: false
-    type: string
-    displayName: Short Description
-    description: a short description of the code
-  long-description:
-    required: false
-    type: string
-    displayName: Long Description
-    description: a long description of the code which may include instruction what actions to take under certain conditions.
-
-example:
-  context: error
-  code: 3001A
-  short-description: Connection Timeout
-  long-description: The allowed time to acquire a database connection has elapsed.  Contact database administrator for TRX_DB on server SCSSOASQL01.

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-code-origin.raml

@@ -1,24 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Origination Point
-description: Information regarding the run-time and design-time location of the code.  When an event occurs in the code, an error or log entry can use this data type to communicate the exact location of the event in the code and the execution environment.
-
-type: object
-
-properties: 
-  node:
-    type: string
-    description: the specific instance name of a container, server, machine etc
-    required: false
-  component:
-    type: string
-    description: the name of the software component, api, service, program, class etc.
-    required: false
-  method:
-    type: string
-    description: the section name of the code in the software component, method, operation, function, subroutine, etc.
-    required: false
-  line:
-    type: string
-    description: the line number of the code in that code unit.
-    required: false

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-contact-information.raml

@@ -1,69 +0,0 @@
-#%RAML 1.0 DataType
-
-uses:
-  language-lib: ../libraries/library-language.raml
-  address-lib: ../libraries/library-address.raml
-  phone-lib: ../libraries/library-phone.raml
-  email-lib: ../libraries/library-email.raml
-  social-media-lib: ../libraries/library-social-media.raml
-
-displayName: Contact Information
-
-type: object
-additionalProperties: false
-
-properties:
-  languages:
-    displayName: List of Languages
-    description:  The preferred language has the highest preference-index number 
-    required: false
-    type: language-lib.languages
-  addresses:
-    displayName: List of Addresses
-    required: false
-    type: address-lib.addresses
-  phones:
-    displayName: List of Phones
-    required: false
-    type: phone-lib.phones
-  emails:
-    displayName: List of Emails
-    required: false
-    type: email-lib.email-addresses
-  social-media-accounts:
-    displayName: List of Social Media Accounts
-    required: false
-    type: social-media-lib.social-media-accounts
-
-example:
-  languages:
-    - name: English
-      code: en
-      preference-index: 1
-    - name: Spanish
-      code: es
-      preference-index: 0
-  addresses:
-    - context: home
-      line1: 3388 Hamilton St
-      line2: Apt 1
-      city: Philadelphia
-      state-region-code: PA
-      country: USA
-      postal-code: "19104"
-      additional-postal-code: "6388"
-    - context: work
-      line1: 101 Walnut St
-      line2: Suite 2300
-      city: Philadelphia
-      state-region-code: PA
-      country: USA
-      postal-code: "19104"
-  phones:
-    - context: home
-      area-code: "212"
-      phone-number: 255-5584
-    - context: work
-      area-code: "212"
-      phone-number: 257-8400
-      ext: "1378"

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-content-data.raml

@@ -1,19 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Content Data
-description: This represents the data part of the content in a printable, non-binary form.  For example, a pdf document can be represented as a binary stream and can be passed around in MIME type application/octet-stream or application/pdf.  That octet stream can also be Base64 encoded and a resulting printable array of characters can be used to represent the same pdf document.  This type is used only for representations that can be printed as an array of characters.  In cases where the content has to be passed as binary application/octet-stream should be used.
-
-type: object
-additionalProperties: true
-
-properties:
-  data:
-    displayName: Base64 Encoded Content Data
-    description: Base64 encoding schemes are commonly used when there is a need to encode binary data that needs be stored and transferred over media that are designed to deal with textual data such as XML or JSON.  This is to ensure that the data remains intact without modification during transport.
-    required: false
-    type: string
-  type:
-    displayName: Data Type
-    description: The data is an array of printable characters.  The type indicates the original form.  For example, if the data is Base64 encoded, and we Base64 decode the data, the resulting output may be a binary for application/pdf or application/msword.
-    required: false
-    

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-content-metadata.raml

@@ -1,243 +0,0 @@
-#%RAML 1.0 DataType
-
-uses:
-  basic-q-lib: ../libraries/library-basic-questions-set.raml
-  property-lib: ../libraries/library-property.raml
-  version-lib: ../libraries/library-version.raml
-  
-displayName: Content Metadata
-description: Data about any content's data.  This type is part of the content type.  However, it can also be used independently as part of a multipart/* where one of the parts describes the metadata and the other parts may be octet stream.
-
-type: object
-additionalProperties: true
-
-properties:
-  content-id:
-    displayName: Content ID
-    description:  The unique ID that represents a content
-    required: false
-    type: string
-  correlated-content-ids:
-    displayName: Correlated content IDs
-    description:  An array of content-ids that are related to this content and their relation type.  Four types of relationships are recognized, namely, parent, child, sibling and associated.
-    required: false
-    type: property-lib.properties
-    examples:
-      parent-only-example:
-        value:
-          - type: parent
-            value: doc-1234567890
-      parent-and-children-example:
-        value:
-          - type: parent
-            value: doc-1234567890
-          - type: child
-            value: doc-1234567999
-          - type: child
-            value: doc-1234560000
-      parent-children-and-siblings-example:
-        value:
-          - type: parent
-            value: doc-1234567890
-          - type: child
-            value: doc-1234567999
-          - type: child
-            value: doc-1234560000
-          - type: sibling
-            value: doc-1234561111
-  content-type:
-    displayName: Content Type
-    description: What type of content is being represented.  Content can be document, image, video, audio, table such as spreadsheets, drawings such as diagrams, or sites that contain content at a referenceable location.
-    required: false
-    enum:
-      - document
-      - image
-      - video
-      - audio
-      - table
-      - drawing
-      - site
-  content-mime-type:
-    displayName: Content MIME Type
-    description: The MIME type of the content, such as application/pdf, image/png, application/msword/ application/epub+zip, application/octet-stream, etc.
-    required: false
-  location:
-    displayName: Location
-    description: |
-      Detailed information about the location of the content.  A content can be a record in a database, a file in a file system, in a referencable site, or some other type of an entry that have not been defined at this point in time.  
-      The ultimate goal of the location property is to "locate" where the content has been persisted.  
-      The consumer originally would not know this information but would get this information from the provider as part of the metadata.
-      An array of name value pairs can generically define any location.
-      location-type: (database | file-system | reference)
-      database: name of the database
-      schema: name of the schema, owner, plan etc.
-      table: name of the table, view, etc.
-      os: name of the operating system
-      file-path: complete path in that operating system
-      file-name: the name of the file where the content has been persisted
-      reference-type: what type of reference is the content located at
-      reference-uri: the uri that shows the exact location of the content
-    required: false
-    type: property-lib.properties
-    example:
-      value:
-        - name: location-type
-          value: database
-        - name: database
-          value: GRC001DB
-        - name: table
-          value: RECORDS
-
-  title:
-    displayName: Title
-    required: false
-    type: string
-    example: Business Architecture for IT Managers
-  subject:
-    displayName: Subject
-    required: false
-    type: string
-    example: Business Architecture Basics
-  author:
-    displayName: Original Author
-    required: false
-    type: string
-  manager:
-    displayName: Author's Manager
-    required: false
-    type: string
-  categories:
-    displayName: Categories
-    description: Content may belong to different categories.  These categories may be used to persist the content in different locations so that their search can be executed more effectively.  For example, contents that contain claim information may be persisted in a claim repository with other claim content, while content that contains application information may be persisted in a different repository.  These line of business categorization may be used to organize content in more manageable ways.  There may be other types of categorizations such as the freshness of the content.  Some active content may be persisted in a location that can read and written very quickly.  Some much older content that has been used but cannot be deleted can be archived.  Even though the location is much harder to reach and much slower to read, the content is still available, yet in a different location.  Since there is no way of knowing how many of these categorization keys are available, this property is an array of name value pairs 
-    required: false
-    type: property-lib.properties
-    example:
-      value:
-        - name: line-of-business
-          value: Individual-Claim
-        - name: freshness
-          value: archived
-  keywords:
-    displayName: Keywords
-    description: Keywords are special informative words that can be tagged to content and later can be used for search and retrieval of that content.
-    required: false
-    type: string[]
-    example: ["Account","Invoice","Correction"]
-  comments:
-    displayName: Comments
-    required: false
-    type: basic-q-lib.basic-questions-sets
-    example:
-      - what: original version created
-        who: Jane Doe
-        when: 2018-08-31T15:42:16.000Z
-      - what: added Chapter 3 for recipies
-        who: Jane Doe
-        when: 2018-09-01T14:42:16.000Z
-  company:
-    displayName: Company that ownes the Content 
-    required: false
-    type: string
-    example: Aflac
-  template-name:
-    displayName: Content Template
-    required: false
-    type: string
-  events:
-    displayName: Important milestone events of the content
-    description:  Important events of a content are the creation, last update, check-in, check-out, print and others.
-    required: false
-    type: basic-q-lib.basic-questions-sets
-    example:
-      - what: created
-        who: Jane Doe
-        when: 2018-08-31T15:42:16.000Z
-      - what: checked-out
-        who: Jane Doe
-        when: 2018-09-01T14:42:16.000Z
-      - what: printed
-        who: Jane Doe
-        when: 2018-09-01T14:52:48.000Z
-      - what: updated
-        who: Jane Doe
-        when: 2018-09-01T15:00:10.000Z
-      - what: checked-in
-        who: Jane Doe
-        when: 2018-09-01T15:10:25.000Z
-  version:
-    displayName: Current Version
-    required: false
-    type: version-lib.version
-  size-in-bytes:
-    displayName: Content Size
-    description: The size of the content's data in bytes
-    required: false
-    type: number
-  custom-fields:
-    displayName: Custom Fields
-    required: false
-    type: property-lib.properties
-examples:
-  read-example:
-    value:
-      content-id: ABCDEF01-2541-3526-AADD-1245789630ABCDEF
-      correlated-content-ids:
-        - type: parent
-          value: doc-1234567890
-        - type: child
-          value: doc-1111
-        - type: sibling
-          value: doc-2222
-      content-type: document
-      content-mime-type: application/pdf
-      location:
-        - name: location-type
-          value: database
-        - name: database
-          value: GRC001DB
-        - name: table
-          value: RECORDS
-      title: Business Architecture for IT Managers
-      subject: Business Architecture Basics
-      author: Dr. John D. Litmus
-      manager: Greg Peterson
-      categories:
-        - name: source
-          value: FileNet
-        - name: line-of-business
-          value: individual claim
-        - name: freshness
-          value: active
-      keywords: 
-        - Account
-        - Invoice
-        - Correction
-      comments:
-        - what: original version created
-          who: Jane Doe
-          when: 2018-08-31T15:42:16.000Z
-        - what: added Chapter 3 for recipies
-          who: Jane Doe
-          when: 2018-09-01T14:42:16.000Z
-      company: Aflac
-      template-name: TMPL-PDF-11234432
-      events:
-        - what: created
-          who: Jane Doe
-          when: 2018-08-31T15:42:16.000Z
-        - what: checked-out
-          who: Jane Doe
-          when: 2018-09-01T14:42:16.000Z
-        - what: printed
-          who: Jane Doe
-          when: 2018-09-01T14:52:48.000Z
-        - what: updated
-          who: Jane Doe
-          when: 2018-09-01T15:00:10.000Z
-        - what: checked-in
-          who: Jane Doe
-          when: 2018-09-01T15:10:25.000Z
-      version:
-        full: 1.0.0
-      size-in-bytes: 155478445
-        

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-content.raml

@@ -1,47 +0,0 @@
-#%RAML 1.0 DataType
-
-uses:
-  content-lib: ../libraries/library-content.raml
-
-displayName: Content
-description: |
-  Content is digitized data that can only be consumed wholly.  There are different types of content, such as document, image, audio, video, table, drawing, etc.
-  Content has two parts
-  1) Data, that is the actual content
-  2) Metadata, that is data about the data.
-  This type is a container of the data and metadata types, so that they can be moved together if needed.
-  This type is used when the content is being passed as an XML or JSON object.  If the data is being passed using a multipart/* MIME type then only the metadata part can be used.
-
-type: object
-additionalProperties: true
-
-properties:
-  content-id:
-    displayName: Content ID
-    description: A unique ID that represents the content.  The same value exists in the metadata section.  It is duplicated here for convenience.
-    required: false
-  
-  content-type:
-    displayName: Content Type
-    description: The type of the content.  The same value exists in the metadata section.  It is duplicated here for convenience.
-    required: false
-    enum:
-      - document
-      - image
-      - video
-      - audio
-      - table
-      - drawing
-      - site
-  
-  data:
-    displayName: Data
-    description: Data
-    required: false
-    type: content-lib.content-data
-
-  metadata:
-    displayName: Metadata
-    description: Metadata
-    required: false
-    type: content-lib.content-metadata

package/demo/apis/SE-11155/1/2/aflac-canonical-definitions/1.0.0/data-types/dataType-contextual.raml

@@ -1,18 +0,0 @@
-#%RAML 1.0 DataType
-
-displayName: Contextual
-description: This is a type that is best used for inheritance to give a context to any inheriting object.
-
-type: object
-additionalProperties: false
-
-properties:
-  context:
-    displayName: Context
-    required: false
-    type: string
-    description: a name that represents the context an object is in.  For example, the context of an email can be 'personal', or 'work', the context of a phone number can be 'office', 'cell', or 'home'.
-    
-examples:
-  json-example:
-    {"context": "work"}