datacontract-cli 0.10.4__py3-none-any.whl → 0.10.5__py3-none-any.whl

datacontract/templates/index.html

@@ -14,7 +14,7 @@
 <div class="min-h-full flex flex-col">
 
   <nav class="bg-white shadow-sm">
-    <div class="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
+    <div class="mx-auto max-w-7xl px-6 lg:px-8">
       <div class="flex h-16 justify-between">
         <div class="flex">
           <div class="flex flex-shrink-0 items-center mr-6">
@@ -32,9 +32,9 @@
 
   <main class="pb-7">
 
-    <div class="pt-5 mx-auto max-w-7xl sm:px-6 lg:px-8">
+    <div class="pt-5 mx-auto max-w-7xl px-6 lg:px-8">
       <div>
-        <div class="lg:flex lg:items-center lg:justify-between px-4 sm:px-0">
+        <div class="lg:flex lg:items-center lg:justify-between px-0">
           <div class="min-w-0 flex-1">
             <h2 class="text-2xl font-bold leading-7 text-gray-900 sm:truncate sm:text-3xl sm:tracking-tight">
               Data Contract Catalog</h2>
@@ -54,8 +54,8 @@
 
             <form aria-labelledby="filter-heading" class="pb-4" >
               <h2 id="filter-heading" class="sr-only">Filters</h2>
-              <div class="flex items-center justify-between">
-                <div class="hidden sm:flex sm:items-baseline sm:space-x-8">
+              <div class="sm:flex items-center justify-between">
+                <div class="sm:flex items-baseline space-x-8">
                   <div>
                     <div class="relative rounded-md shadow-sm">
                       <div class="pointer-events-none absolute inset-y-0 left-0 flex items-center pl-3">
@@ -63,7 +63,7 @@
                           <path fill-rule="evenodd" d="M9 3.5a5.5 5.5 0 100 11 5.5 5.5 0 000-11zM2 9a7 7 0 1112.452 4.391l3.328 3.329a.75.75 0 11-1.06 1.06l-3.329-3.328A7 7 0 012 9z" clip-rule="evenodd" />
                         </svg>
                       </div>
-                      <input type="text" name="q" id="search" class="block w-72 rounded-md border-0 py-1.5 pl-10 text-gray-900 ring-1 ring-inset ring-gray-300 placeholder:text-gray-400 focus:ring-2 focus:ring-inset focus:ring-indigo-600 sm:text-sm sm:leading-6" placeholder="Search">
+                      <input type="text" name="q" id="search" class="block w-full sm:w-72 rounded-md border-0 py-1.5 pl-10 text-gray-900 ring-1 ring-inset ring-gray-300 placeholder:text-gray-400 focus:ring-2 focus:ring-inset focus:ring-indigo-600 sm:text-sm sm:leading-6" placeholder="Search">
                     </div>
                   </div>
                 </div>

datacontract/templates/style/output.css

@@ -781,10 +781,6 @@ video {
   width: 58.333333%;
 }
 
-.w-72 {
-  width: 18rem;
-}
-
 .w-9\/12 {
   width: 75%;
 }
@@ -841,6 +837,10 @@ video {
   align-items: center;
 }
 
+.items-baseline {
+  align-items: baseline;
+}
+
 .justify-center {
   justify-content: center;
 }
@@ -888,6 +888,12 @@ video {
   margin-left: calc(1.5rem * calc(1 - var(--tw-space-x-reverse)));
 }
 
+.space-x-8 > :not([hidden]) ~ :not([hidden]) {
+  --tw-space-x-reverse: 0;
+  margin-right: calc(2rem * var(--tw-space-x-reverse));
+  margin-left: calc(2rem * calc(1 - var(--tw-space-x-reverse)));
+}
+
 .space-y-6 > :not([hidden]) ~ :not([hidden]) {
   --tw-space-y-reverse: 0;
   margin-top: calc(1.5rem * calc(1 - var(--tw-space-y-reverse)));
@@ -1004,6 +1010,11 @@ video {
   padding: 1.5rem;
 }
 
+.px-0 {
+  padding-left: 0px;
+  padding-right: 0px;
+}
+
 .px-1 {
   padding-left: 0.25rem;
   padding-right: 0.25rem;
@@ -1376,6 +1387,10 @@ video {
     width: 80%;
   }
 
+  .sm\:w-72 {
+    width: 18rem;
+  }
+
   .sm\:grid-cols-2 {
     grid-template-columns: repeat(2, minmax(0, 1fr));
   }
@@ -1392,22 +1407,12 @@ video {
     align-items: center;
   }
 
-  .sm\:items-baseline {
-    align-items: baseline;
-  }
-
   .sm\:space-x-6 > :not([hidden]) ~ :not([hidden]) {
     --tw-space-x-reverse: 0;
     margin-right: calc(1.5rem * var(--tw-space-x-reverse));
     margin-left: calc(1.5rem * calc(1 - var(--tw-space-x-reverse)));
   }
 
-  .sm\:space-x-8 > :not([hidden]) ~ :not([hidden]) {
-    --tw-space-x-reverse: 0;
-    margin-right: calc(2rem * var(--tw-space-x-reverse));
-    margin-left: calc(2rem * calc(1 - var(--tw-space-x-reverse)));
-  }
-
   .sm\:truncate {
     overflow: hidden;
     text-overflow: ellipsis;

{datacontract_cli-0.10.4.dist-info → datacontract_cli-0.10.5.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: datacontract-cli
-Version: 0.10.4
+Version: 0.10.5
 Summary: Test data contracts
 Author-email: Jochen Christ <jochen.christ@innoq.com>, Stefan Negele <stefan.negele@innoq.com>
 Project-URL: Homepage, https://cli.datacontract.com
@@ -14,30 +14,33 @@ License-File: LICENSE
 Requires-Dist: typer[all] <0.13,>=0.9
 Requires-Dist: pydantic <2.8.0,>=2.5.3
 Requires-Dist: pyyaml ~=6.0.1
-Requires-Dist: requests ~=2.31.0
+Requires-Dist: requests <2.33,>=2.31
 Requires-Dist: fastapi ==0.111.0
-Requires-Dist: fastparquet ==2024.2.0
+Requires-Dist: fastparquet ==2024.5.0
 Requires-Dist: python-multipart ==0.0.9
 Requires-Dist: rich ~=13.7.0
-Requires-Dist: simple-ddl-parser ==1.3.0
+Requires-Dist: simple-ddl-parser ==1.5.1
 Requires-Dist: soda-core-bigquery <3.4.0,>=3.3.1
 Requires-Dist: soda-core-duckdb <3.4.0,>=3.3.1
+Requires-Dist: soda-core-sqlserver <3.4.0,>=3.3.1
 Requires-Dist: soda-core-postgres <3.4.0,>=3.3.1
 Requires-Dist: soda-core-snowflake <3.4.0,>=3.3.1
 Requires-Dist: soda-core-spark[databricks] <3.4.0,>=3.3.1
+Requires-Dist: databricks-sql-connector <3.2.0,>=3.1.2
 Requires-Dist: soda-core-spark-df <3.4.0,>=3.3.1
+Requires-Dist: setuptools >=60
 Requires-Dist: snowflake-connector-python[pandas] <3.11,>=3.6
-Requires-Dist: duckdb ==0.10.2
+Requires-Dist: duckdb ==0.10.3
 Requires-Dist: fastjsonschema ~=2.19.1
 Requires-Dist: python-dotenv ~=1.0.0
-Requires-Dist: s3fs ==2024.3.1
+Requires-Dist: s3fs ==2024.5.0
 Requires-Dist: rdflib ==7.0.0
 Requires-Dist: avro ==1.11.3
-Requires-Dist: opentelemetry-exporter-otlp-proto-grpc ~=1.16.0
-Requires-Dist: opentelemetry-exporter-otlp-proto-http ~=1.16.0
+Requires-Dist: opentelemetry-exporter-otlp-proto-grpc ~=1.16
+Requires-Dist: opentelemetry-exporter-otlp-proto-http ~=1.16
 Requires-Dist: deltalake ~=0.17.0
-Requires-Dist: boto3 <1.34.99,>=1.34.41
-Requires-Dist: botocore <1.34.99,>=1.34.41
+Requires-Dist: boto3 <1.34.114,>=1.34.41
+Requires-Dist: botocore <1.34.114,>=1.34.41
 Requires-Dist: jinja-partials >=0.2.1
 Provides-Extra: dev
 Requires-Dist: httpx ==0.27.0 ; extra == 'dev'
@@ -45,10 +48,12 @@ Requires-Dist: ruff ; extra == 'dev'
 Requires-Dist: pytest ; extra == 'dev'
 Requires-Dist: pytest-xdist ; extra == 'dev'
 Requires-Dist: moto ; extra == 'dev'
+Requires-Dist: pymssql ==2.3.0 ; extra == 'dev'
 Requires-Dist: testcontainers <4.0.0 ; extra == 'dev'
 Requires-Dist: testcontainers-minio ; extra == 'dev'
 Requires-Dist: testcontainers-postgres ; extra == 'dev'
 Requires-Dist: testcontainers-kafka ; extra == 'dev'
+Requires-Dist: testcontainers[mssql] ; extra == 'dev'
 
 # Data Contract CLI
 
@@ -68,7 +73,7 @@ It uses data contract YAML files to lint the data contract, connect to data sour
 
 ## Getting started
 
-Let's look at this data contract:  
+Let's look at this data contract:
 [https://datacontract.com/examples/orders-latest/datacontract.yaml](https://datacontract.com/examples/orders-latest/datacontract.yaml)
 
 We have a _servers_ section with endpoint details to the S3 bucket, _models_ for the structure of the data, _servicelevels_ and _quality_ attributes that describe the expected freshness and number of rows.
@@ -240,11 +245,11 @@ Commands
 
 ### init
 
-```                                                                                                
- Usage: datacontract init [OPTIONS] [LOCATION]                                                  
-                                                                                                
- Download a datacontract.yaml template and write it to file.                                    
-                                                                                                
+```
+ Usage: datacontract init [OPTIONS] [LOCATION]
+
+ Download a datacontract.yaml template and write it to file.
+
 ╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────╮
 │   location      [LOCATION]  The location (url or path) of the data contract yaml to create. │
 │                             [default: datacontract.yaml]                                    │
@@ -262,10 +267,10 @@ Commands
 ### lint
 
 ```
- Usage: datacontract lint [OPTIONS] [LOCATION]                                                                                     
-                                                                                                                                   
- Validate that the datacontract.yaml is correctly formatted.                                                                       
-                                                                                                                                   
+ Usage: datacontract lint [OPTIONS] [LOCATION]
+
+ Validate that the datacontract.yaml is correctly formatted.
+
 ╭─ Arguments ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │   location      [LOCATION]  The location (url or path) of the data contract yaml. [default: datacontract.yaml]                 │
 ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
@@ -279,10 +284,10 @@ Commands
 ### test
 
 ```
- Usage: datacontract test [OPTIONS] [LOCATION]                                                                                     
-                                                                                                                                   
- Run schema and quality tests on configured servers.                                                                               
-                                                                                                                                   
+ Usage: datacontract test [OPTIONS] [LOCATION]
+
+ Run schema and quality tests on configured servers.
+
 ╭─ Arguments ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │   location      [LOCATION]  The location (url or path) of the data contract yaml. [default: datacontract.yaml]                 │
 ╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
@@ -315,11 +320,11 @@ Data Contract CLI connects to a data source and runs schema and quality tests to
 $ datacontract test --server production datacontract.yaml
 ```
 
-To connect to the databases the `server` block in the datacontract.yaml is used to set up the connection. 
+To connect to the databases the `server` block in the datacontract.yaml is used to set up the connection.
 In addition, credentials, such as username and passwords, may be defined with environment variables.
 
 The application uses different engines, based on the server `type`.
-Internally, it connects with DuckDB, Spark, or a native connection and executes the most tests with _soda-core_ and _fastjsonschema_. 
+Internally, it connects with DuckDB, Spark, or a native connection and executes the most tests with _soda-core_ and _fastjsonschema_.
 
 Credentials are provided with environment variables.
 
@@ -505,7 +510,7 @@ dbutils.library.restartPython()
 from datacontract.data_contract import DataContract
 
 data_contract = DataContract(
-  data_contract_file="/Volumes/acme_catalog_prod/orders_latest/datacontract/datacontract.yaml", 
+  data_contract_file="/Volumes/acme_catalog_prod/orders_latest/datacontract/datacontract.yaml",
   spark=spark)
 run = data_contract.test()
 run.result
@@ -530,7 +535,7 @@ servers:
 models:
   my_table_1: # corresponds to a table
     type: table
-    fields: 
+    fields:
       my_column_1: # corresponds to a column
         type: varchar
 ```
@@ -588,7 +593,7 @@ servers:
 models:
   my_table_1: # corresponds to a table
     type: table
-    fields: 
+    fields:
       my_column_1: # corresponds to a column
         type: varchar
 ```
@@ -602,38 +607,78 @@ models:
 
 
 
+
+### Postgres
+
+Data Contract CLI can test data in Postgres or Postgres-compliant databases (e.g., RisingWave).
+
+#### Example
+
+datacontract.yaml
+```yaml
+servers:
+  postgres:
+    type: sqlserver
+    host: localhost
+    port: 5432
+    database: tempdb
+    schema: dbo
+    driver: ODBC Driver 18 for SQL Server
+models:
+  my_table_1: # corresponds to a table
+    type: table
+    fields:
+      my_column_1: # corresponds to a column
+        type: varchar
+```
+
+#### Environment Variables
+
+| Environment Variable             | Example            | Description |
+|----------------------------------|--------------------|-------------|
+| `DATACONTRACT_SQLSERVER_USERNAME` | `root`         | Username    |
+| `DATACONTRACT_SQLSERVER_PASSWORD` | `toor` | Password    |
+| `DATACONTRACT_SQLSERVER_TRUSTED_CONNECTION` | `True` | Use windows authentication, instead of login    |
+| `DATACONTRACT_SQLSERVER_TRUST_SERVER_CERTIFICATE` | `True` | Trust self-signed certificate    |
+| `DATACONTRACT_SQLSERVER_ENCRYPTED_CONNECTION` | `True` | Use SSL    |
+
+
+
 ### export
 
 ```
+
  Usage: datacontract export [OPTIONS] [LOCATION]                                                                                                                           
                                                                                                                                                                            
  Convert data contract to a specific format. Prints to stdout or to the specified output file.                                                                                                     
                                                                                                                                                                            
-╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
-│   location      [LOCATION]  The location (url or path) of the data contract yaml. [default: datacontract.yaml]                                   │
-╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
-╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
-│ *  --format        [jsonschema|pydantic-model|sodacl|dbt|dbt-sources|dbt-staging  The export format. [default: None] [required]                  │
-│                    -sql|odcs|rdf|avro|protobuf|great-expectations|terraform|avro                                                                 │
-│                    -idl|sql|sql-query|html|bigquery|go]                                                                                             │
-│    --output        PATH                                                           Specify the file path where the exported data will be saved.   │
-│                                                                                   If no path is provided, the output will be printed to stdout.  │
-│                                                                                   [default: None]                                                │
-│    --server        TEXT                                                           The server name to export. [default: None]                     │
-│    --model         TEXT                                                           Use the key of the model in the data contract yaml file to     │
-│                                                                                   refer to a model, e.g., `orders`, or `all` for all models      │
-│                                                                                   (default).                                                     │
-│                                                                                   [default: all]                                                 │
-│    --help                                                                         Show this message and exit.                                    │
-╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
-╭─ RDF Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
-│ --rdf-base        TEXT  [rdf] The base URI used to generate the RDF graph. [default: None]                                                       │
-╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
-╭─ SQL Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
-│ --sql-server-type        TEXT  [sql] The server type to determine the sql dialect. By default, it uses 'auto' to automatically detect the sql    │
-│                                dialect via the specified servers in the data contract.                                                           │
-│                                [default: auto]                                                                                                   │
-╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Arguments ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│   location      [LOCATION]  The location (url or path) of the data contract yaml. [default: datacontract.yaml]                 │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ *  --format        [jsonschema|pydantic-model|sodacl|dbt|dbt-sources|db  The export format. [default: None] [required]         │
+│                    t-staging-sql|odcs|rdf|avro|protobuf|great-expectati                                                        │
+│                    ons|terraform|avro-idl|sql|sql-query|html|go|bigquer                                                        │
+│                    y|dbml]                                                                                                     │
+│    --output        PATH                                                  Specify the file path where the exported data will be │
+│                                                                          saved. If no path is provided, the output will be     │
+│                                                                          printed to stdout.                                    │
+│                                                                          [default: None]                                       │
+│    --server        TEXT                                                  The server name to export. [default: None]            │
+│    --model         TEXT                                                  Use the key of the model in the data contract yaml    │
+│                                                                          file to refer to a model, e.g., `orders`, or `all`    │
+│                                                                          for all models (default).                             │
+│                                                                          [default: all]                                        │
+│    --help                                                                Show this message and exit.                           │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ RDF Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --rdf-base        TEXT  [rdf] The base URI used to generate the RDF graph. [default: None]                                     │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ SQL Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --sql-server-type        TEXT  [sql] The server type to determine the sql dialect. By default, it uses 'auto' to automatically │
+│                                detect the sql dialect via the specified servers in the data contract.                          │
+│                                [default: auto]                                                                                 │
+╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 
 ```
 
@@ -646,9 +691,9 @@ Available export options:
 
 | Type                 | Description                                             | Status |
 |----------------------|---------------------------------------------------------|--------|
-| `html`               | Export to HTML                                          | ✅     | 
-| `jsonschema`         | Export to JSON Schema                                   | ✅     | 
-| `odcs`               | Export to Open Data Contract Standard (ODCS)            | ✅     | 
+| `html`               | Export to HTML                                          | ✅     |
+| `jsonschema`         | Export to JSON Schema                                   | ✅     |
+| `odcs`               | Export to Open Data Contract Standard (ODCS)            | ✅     |
 | `sodacl`             | Export to SodaCL quality checks in YAML format          | ✅     |
 | `dbt`                | Export to dbt models in YAML format                     | ✅     |
 | `dbt-sources`        | Export to dbt sources in YAML format                    | ✅     |
@@ -663,15 +708,16 @@ Available export options:
 | `bigquery`           | Export to BigQuery Schemas                              | ✅     |
 | `go`                 | Export to Go types                                      | ✅     |
 | `pydantic-model`     | Export to pydantic models                               | ✅     |
+| `DBML`               | Export to a DBML Diagram description                    | ✅     |
 | Missing something?   | Please create an issue on GitHub                        | TBD    |
 
 #### Great Expectations
 
-The export function transforms a specified data contract into a comprehensive Great Expectations JSON suite. 
+The export function transforms a specified data contract into a comprehensive Great Expectations JSON suite.
 If the contract includes multiple models, you need to specify the names of the model you wish to export.
 
 ```shell
-datacontract  export datacontract.yaml --format great-expectations --model orders 
+datacontract  export datacontract.yaml --format great-expectations --model orders
 ```
 
 The export creates a list of expectations by utilizing:
@@ -681,7 +727,7 @@ The export creates a list of expectations by utilizing:
 
 #### RDF
 
-The export function converts a given data contract into a RDF representation. You have the option to 
+The export function converts a given data contract into a RDF representation. You have the option to
 add a base_url which will be used as the default prefix to resolve relative IRIs inside the document.
 
 ```shell
@@ -703,6 +749,54 @@ Having the data contract inside an RDF Graph gives us access the following use c
 - Apply graph algorithms on multiple data contracts (Find similar data contracts, find "gatekeeper"
 data products, find the true domain owner of a field attribute)
 
+#### DBML
+
+The export function converts the logical data types of the datacontract into the specific ones of a concrete Database
+if a server is selected via the `--server` option (based on the `type` of that server). If no server is selected, the 
+logical data types are exported.
+
+
+#### Avro
+
+The export function converts the data contract specification into an avro schema. It supports specifying custom avro properties for logicalTypes and default values. 
+
+##### Custom Avro Properties
+
+We support a **config map on field level**. A config map may include any additional key-value pairs and support multiple server type bindings.
+
+To specify custom Avro properties in your data contract, you can define them within the `config` section of your field definition. Below is an example of how to structure your YAML configuration to include custom Avro properties, such as `avroLogicalType` and `avroDefault`.
+
+>NOTE: At this moment, we just support [logicalType](https://avro.apache.org/docs/1.11.0/spec.html#Logical+Types) and [default](https://avro.apache.org/docs/1.11.0/spec.htm)
+
+#### Example Configuration
+
+```yaml
+models:
+  orders:
+    fields:
+      my_field_1:
+        description: Example for AVRO with Timestamp (microsecond precision) https://avro.apache.org/docs/current/spec.html#Local+timestamp+%28microsecond+precision%29
+        type: long
+        example: 1672534861000000  # Equivalent to 2023-01-01 01:01:01 in microseconds
+        config:          
+          avroLogicalType: local-timestamp-micros
+          avroDefault: 1672534861000000
+```
+
+#### Explanation
+
+- **models**: The top-level key that contains different models (tables or objects) in your data contract.
+- **orders**: A specific model name. Replace this with the name of your model.
+- **fields**: The fields within the model. Each field can have various properties defined.
+- **my_field_1**: The name of a specific field. Replace this with your field name.
+  - **description**: A textual description of the field.
+  - **type**: The data type of the field. In this example, it is `long`.
+  - **example**: An example value for the field.
+  - **config**: Section to specify custom Avro properties.
+    - **avroLogicalType**: Specifies the logical type of the field in Avro. In this example, it is `local-timestamp-micros`.
+    - **avroDefault**: Specifies the default value for the field in Avro. In this example, it is 1672534861000000 which corresponds to ` 2023-01-01 01:01:01 UTC`.
+
+
 ### import
 
 ```
@@ -727,7 +821,7 @@ In this case there's no need to specify `source` but instead `bt-project-id`, `b
 
 For providing authentication to the Client, please see [the google documentation](https://cloud.google.com/docs/authentication/provide-credentials-adc#how-to) or the one [about authorizing client libraries](https://cloud.google.com/bigquery/docs/authentication#client-libs).
 
-Example: 
+Example:
 ```bash
 # Example import from SQL DDL
 datacontract import --format sql --source my_ddl.sql
@@ -761,10 +855,10 @@ Available import options:
 ### breaking
 
 ```
- Usage: datacontract breaking [OPTIONS] LOCATION_OLD LOCATION_NEW                                                            
-                                                                                                                             
- Identifies breaking changes between data contracts. Prints to stdout.                                                       
-                                                                                                                             
+ Usage: datacontract breaking [OPTIONS] LOCATION_OLD LOCATION_NEW
+
+ Identifies breaking changes between data contracts. Prints to stdout.
+
 ╭─ Arguments ───────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │ *    location_old      TEXT  The location (url or path) of the old data contract yaml. [default: None] [required]        │
 │ *    location_new      TEXT  The location (url or path) of the new data contract yaml. [default: None] [required]        │
@@ -777,10 +871,10 @@ Available import options:
 ### changelog
 
 ```
- Usage: datacontract changelog [OPTIONS] LOCATION_OLD LOCATION_NEW                                                           
-                                                                                                                             
- Generate a changelog between data contracts. Prints to stdout.                                                              
-                                                                                                                             
+ Usage: datacontract changelog [OPTIONS] LOCATION_OLD LOCATION_NEW
+
+ Generate a changelog between data contracts. Prints to stdout.
+
 ╭─ Arguments ───────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │ *    location_old      TEXT  The location (url or path) of the old data contract yaml. [default: None] [required]        │
 │ *    location_new      TEXT  The location (url or path) of the new data contract yaml. [default: None] [required]        │
@@ -793,10 +887,10 @@ Available import options:
 ### diff
 
 ```
- Usage: datacontract diff [OPTIONS] LOCATION_OLD LOCATION_NEW                                                                
-                                                                                                                             
- PLACEHOLDER. Currently works as 'changelog' does.                                                                           
-                                                                                                                             
+ Usage: datacontract diff [OPTIONS] LOCATION_OLD LOCATION_NEW
+
+ PLACEHOLDER. Currently works as 'changelog' does.
+
 ╭─ Arguments ───────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │ *    location_old      TEXT  The location (url or path) of the old data contract yaml. [default: None] [required]        │
 │ *    location_new      TEXT  The location (url or path) of the new data contract yaml. [default: None] [required]        │
@@ -928,14 +1022,14 @@ Create a data contract based on the requirements from use cases.
    ```bash
    $ datacontract init
    ```
-   
+
 2. Add examples to the `datacontract.yaml`. Do not start with the data model, although you are probably tempted to do that. Examples are the fastest way to get feedback from everybody and not loose someone in the discussion.
 
 3. Create the model based on the examples. Test the model against the examples to double-check whether the model matches the examples.
     ```bash
     $ datacontract test --examples
     ```
-   
+
 4. Add quality checks and additional type constraints one by one to the contract and make sure the examples and the actual data still adheres to the contract. Check against examples for a very fast feedback loop.
     ```bash
     $ datacontract test --examples