chore: Bundle and split the sample to get updated output (#100)

keep the README files, and allow the full `info.description` since ref
isn't valid here

Author: lornajane

openapi/code_samples/csharp/echo/post.cs openapi/code_samples/C_sharp/echo/post.csopenapi/code_samples/csharp/echo/post.cs renamed to openapi/code_samples/C_sharp/echo/post.cs

@@ -2,4 +2,4 @@ description: Problem
 content:
   application/problem+json:
     schema:
-      $ref: ../schemas/Problem.yaml
+      $ref: ../schemas/Problem.yaml

openapi/components/responses/Problem.yaml

@@ -2,38 +2,33 @@ type: object
 additionalProperties: true
 minProperties: 1
 description: >-
-  The Problem Details JSON Object [[RFC7807](https://tools.ietf.org/html/rfc7807)].
+  The Problem Details JSON Object
+  [[RFC7807](https://tools.ietf.org/html/rfc7807)].
 properties:
   type:
     type: string
     description: >-
-      A URI reference [[RFC3986](https://tools.ietf.org/html/rfc3986)] that identifies the problem type.
-      It should provide human-readable documentation for the problem type.
-      When this member is not present, its value is assumed to be "about:blank".
+      A URI reference [[RFC3986](https://tools.ietf.org/html/rfc3986)] that
+      identifies the problem type. It should provide human-readable
+      documentation for the problem type. When this member is not present, its
+      value is assumed to be "about:blank".
     format: uri
   title:
     type: string
     description: >-
-      A short, human-readable summary of the problem type.
-      It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
+      A short, human-readable summary of the problem type. It SHOULD NOT change
+      from occurrence to occurrence of the problem, except for purposes of
+      localization.
   status:
     type: integer
     description: The HTTP status code.
     minimum: 400
     maximum: 599
   detail:
     type: string
-    description: >-
-      A human-readable explanation specific to this
-      occurrence of the problem.
+    description: A human-readable explanation specific to this occurrence of the problem.
   instance:
     type: string
     description: >-
-      A URI reference that identifies the specific
-      occurrence of the problem.  It may or may not yield further
-      information if dereferenced.
-
-#    Consumers SHOULD NOT parse the "detail" member for information;
-#    extensions are more suitable and less error-prone ways to obtain such
-#    information.
-#    See: https://datatracker.ietf.org/doc/html/rfc7807#section-3.2
+      A URI reference that identifies the specific occurrence of the problem. 
+      It may or may not yield further information if dereferenced.

openapi/components/schemas/Problem.yaml

@@ -42,7 +42,7 @@ properties:
     description: Property name's description (type is string or null)
     type:
       - string
-      - "null"
+      - 'null'
     examples:
       - example
   stringEnumValues:

openapi/components/schemas/Schema.yaml

@@ -2,17 +2,42 @@ openapi: 3.1.0
 info:
   version: 1.0.0
   title: Example.com
-  termsOfService: 'https://example.com/terms/'
+  termsOfService: https://example.com/terms/
   contact:
     email: [email protected]
-    url: 'http://example.com/contact'
+    url: http://example.com/contact
   license:
     name: Apache 2.0
-    url: 'http://www.apache.org/licenses/LICENSE-2.0.html'
+    url: http://www.apache.org/licenses/LICENSE-2.0.html
   x-logo:
-    url: 'https://redocly.github.io/openapi-template/logo.png'
-  description:
-    $ref: ./info-description.md
+    url: https://redocly.github.io/openapi-template/logo.png
+  description: >
+    This is an **example** API to demonstrate features of the OpenAPI
+    specification.
+
+    # Introduction
+
+    This API definition is intended to to be a good starting point for
+    describing your API in [OpenAPI/Swagger
+    format](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md).
+
+    It also demonstrates features of the
+    [create-openapi-repo](https://github.com/Redocly/create-openapi-repo) tool
+    and the [Redoc](https://github.com/Redocly/Redoc) documentation engine. Beyond
+    the standard OpenAPI syntax, we use a few 
+    [vendor extensions](https://github.com/Redocly/Redoc/blob/master/docs/redoc-vendor-extensions.md).
+
+    # OpenAPI Specification
+
+    The goal of The OpenAPI Specification is to define a standard, language-agnostic interface to REST APIs which
+    allows both humans and computers to discover and understand the capabilities
+    of the service without access to source
+    code, documentation, or through network traffic inspection. When properly
+    defined via OpenAPI, a consumer can 
+    understand and interact with the remote service with a minimal amount of
+    implementation logic. Similar to what
+    interfaces have done for lower-level programming, OpenAPI removes the
+    guesswork in calling the service.
 tags:
   - name: Echo
     description: Example echo operations.
@@ -21,31 +46,31 @@ tags:
   - name: Tag
     description: This is a tag description.
 servers:
-  - url: 'https://{tenant}/api/v1'
+  - url: https://{tenant}/api/v1
     variables:
       tenant:
         default: www
         description: Your tenant id
-  - url: 'https://example.com/api/v1'
+  - url: https://example.com/api/v1
 paths:
-  '/users/{username}':
-    $ref: 'paths/users_{username}.yaml'
+  /users/{username}:
+    $ref: paths/users_{username}.yaml
   /echo:
     $ref: paths/echo.yaml
   /pathItem:
-    $ref: paths/path-item.yaml
+    $ref: paths/pathItem.yaml
   /pathItemWithExamples:
-    $ref: paths/path-item-with-examples.yaml
+    $ref: paths/pathItemWithExamples.yaml
 components:
   securitySchemes:
     main_auth:
       type: oauth2
       flows:
         implicit:
-          authorizationUrl: 'http://example.com/api/oauth/dialog'
+          authorizationUrl: http://example.com/api/oauth/dialog
           scopes:
-            'read:users': read users info
-            'write:users': modify or remove users
+            read:users: read users info
+            write:users: modify or remove users
     api_key:
       type: apiKey
       in: header

openapi/components/securitySchemes/api_key.yaml

@@ -31,7 +31,7 @@ post:
         text/csv:
           schema:
             type: string
-    '400': 
+    '400':
       description: Unauthorized
   requestBody:
     content:
@@ -46,9 +46,9 @@ post:
     description: Echo payload
     required: true
   x-codeSamples:
-    - lang: "C#"
+    - lang: C#
       source:
-        $ref: "../code_samples/csharp/echo/post.cs"
+        $ref: ../code_samples/C_sharp/echo/post.cs
     - lang: PHP
       source:
         $ref: ../code_samples/PHP/echo/post.php