feat!: release v6

.github/workflows/if-nodejs-release.yml

@@ -141,4 +141,4 @@ jobs:
           fields: repo,action,workflow
           text: 'Release workflow failed in release job'
         env:
-          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}
+          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_CI_FAIL_NOTIFY }}

.github/workflows/runtime-go-testing.yml

@@ -2,31 +2,36 @@
 on:
   push:
   pull_request:
-  types: [opened, reopened, synchronize, ready_for_review]
-  paths:
-    - 'src/generators/go/**'
-    - 'test/runtime/runtime-go/**'
-    - test/runtime/**go**
+    types: [opened, reopened, synchronize, ready_for_review]
+    paths:
+      - 'src/generators/go/**'
+      - 'test/runtime/runtime-go/**'
+      - 'test/runtime/**go**'
 
 jobs:
-  test: 
-  name: Runtime testing Go Models
-  if: "github.event.pull_request.draft == false &&!((github.actor == 'asyncapi-bot' && startsWith(github.event.pull_request.title, 'ci: update global workflows')) || (github.actor == 'asyncapi-bot' && startsWith(github.event.pull_request.title, 'chore(release):')) || (github.actor == 'allcontributors' && startsWith(github.event.pull_request.title, 'docs: add')))"
-  runs-on: ubuntu-latest
-  steps: 
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Setup Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: 14
-    - name: Build Library
-      run: npm install && npm run build:prod
-    - name: Setup Go
-      uses: actions/setup-go@v2
-      with:
-        go-version: 1.20
-    -name: Generate Go Models
-      run: npm run generate:runtime:go
-    -name: Run runtime Tests
-      run: npm run test:runtime:go
+  test:
+    name: Runtime testing Go Models
+    if: "github.event.pull_request.draft == false &&!((github.actor == 'asyncapi-bot' && startsWith(github.event.pull_request.title, 'ci: update global workflows')) || (github.actor == 'asyncapi-bot' && startsWith(github.event.pull_request.title, 'chore(release):')) || (github.actor == 'allcontributors' && startsWith(github.event.pull_request.title, 'docs: add')))"
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+      - name: Check package-lock version
+        uses: asyncapi/.github/.github/actions/get-node-version-from-package-lock@master
+        id: lockversion
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "${{ steps.lockversion.outputs.version }}"
+          cache: 'npm'
+          cache-dependency-path: '**/package-lock.json'
+      - name: Build Library
+        run: npm install && npm run build:prod
+      - name: Setup Go
+        uses: actions/setup-go@v4
+        with:
+          go-version: '1.22'
+      - name: Generate Go Models
+        run: npm run generate:runtime:go
+      - name: Run runtime Tests
+        run: npm run test:runtime:go

.github/workflows/runtime-kotlin-testing.yml

@@ -15,22 +15,22 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Check package-lock version
         uses: asyncapi/.github/.github/actions/get-node-version-from-package-lock@master
         id: lockversion
       - name: Setup Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: "${{ steps.lockversion.outputs.version }}"
           cache: 'npm'
           cache-dependency-path: '**/package-lock.json'
       - name: Build library
         run: npm install && npm run build:prod
       - name: Setup Java
-        uses: actions/setup-java@v2
+        uses: actions/setup-java@v4
         with:
-          distribution: 'adopt'
+          distribution: 'temurin'
           java-version: '11'
       - name: Generate Kotlin models
         run: npm run generate:runtime:kotlin 

.gitignore

@@ -14,4 +14,5 @@ java_runtime_node
 .scala-build
 
 .cursorrules
-.cursor
+.cursor
+.claude

.nvmrc

@@ -1 +1 @@
-v18
+v22

Dockerfile

@@ -1,4 +1,4 @@
-FROM openjdk:16.0.1-jdk-slim-buster
+FROM eclipse-temurin:21-jdk-bookworm
 
 # Install updates
 RUN apt-get update -yq \
@@ -12,33 +12,34 @@ RUN curl -fsSL https://deb.nodesource.com/setup_lts.x | bash - \
     && apt-get install -yq nodejs
 
 # Install golang
-RUN curl -fsSL https://golang.org/dl/go1.16.8.linux-amd64.tar.gz | tar -C /usr/local -xz
+ARG TARGETARCH
+RUN curl -fsSL "https://go.dev/dl/go1.22.4.linux-${TARGETARCH}.tar.gz" | tar -C /usr/local -xz
 ENV PATH="${PATH}:/usr/local/go/bin"
 
 # Install dotnet SDK
 RUN apt install apt-transport-https dirmngr gnupg ca-certificates -yq  \
     && apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF \
-    && echo "deb https://download.mono-project.com/repo/debian stable-buster main" | tee /etc/apt/sources.list.d/mono-official-stable.list \
+    && echo "deb https://download.mono-project.com/repo/debian stable-bookworm main" | tee /etc/apt/sources.list.d/mono-official-stable.list \
     && apt update -yq  \
     && apt install mono-devel -yq
 
 # Install rust
 RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
 
 # Install Python
-RUN apt-get install -yq python
+RUN apt-get install -yq python3
 
 # Install Kotlin
 RUN apt install -yq wget unzip  \
     && cd /usr/lib \
     && wget -q https://github.com/JetBrains/kotlin/releases/download/v1.8.0/kotlin-compiler-1.8.0.zip \
     && unzip -qq kotlin-compiler-*.zip
 
-ENV PATH $PATH:/usr/lib/kotlinc/bin
+ENV PATH="${PATH}:/usr/lib/kotlinc/bin"
 
 # Install PHP
 RUN wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg \
-    && echo "deb https://packages.sury.org/php/ buster main" > /etc/apt/sources.list.d/php.list \
+    && echo "deb https://packages.sury.org/php/ bookworm main" > /etc/apt/sources.list.d/php.list \
     && apt-get update -yq \
     && apt-get install -y php8.2
 

docs/advanced.md

@@ -15,7 +15,6 @@ This document contains many of the advanced use-cases that you may stumble upon
 - [Change the generated indentation type and size](#change-the-generated-indentation-type-and-size)
 - [Change the type mapping](#change-the-type-mapping)
 - [Changing the constrain rules](#changing-the-constrain-rules)
-- [Customizing the interpreter options](#customizing-the-interpreter-options)
 
 <!-- tocstop -->
 
@@ -104,15 +103,3 @@ There can be multiple reasons why you want to change the default constrain rules
 Check out this [example out for a live demonstration](../examples/overwrite-default-constraint/) for how to overwrite the default constraints.
 
 Check out this [example out for a live demonstration](../examples/overwrite-naming-formatting/) for how to overwrite the naming formatting for models.
-
-## Customizing the interpreter options
-
-According to JSON schema draft 7, if `additionalProperties` or `additionalItems` are omitted, their default value is `true`. The `Interpreter` honors this behavior, however this creates more loose models that might not be the intention for the developer. 
-
-We suggest not using this option if it can be avoided, as it limits your generated models to include any additional properties, and would simply be ignored. Instead adapt your schemas to be more strict by setting these keywords to `false`. This option should really only be used when you have no control over your input and the output is unintended.
-
-To set the interpreter up to ignore the default behavior, you can further restrict your models with the following options:
-- `ignoreAdditionalProperties` - if set, it ensures that `additionalProperties` by default is ignored.
-- `ignoreAdditionalItems` - if set, it ensures that `additionalItems` by default is ignored.
-
-Check out this [example out for a live demonstration](../examples/passing-interpreter-options/) for how to customize the behavior of `additionalProperties`.

docs/inputs/JSON_Schema.md

@@ -1,4 +1,115 @@
-# Interpretation of JSON Schema to CommonModel
+# JSON Schema as an input
+
+## Processor Options
+
+The JSON Schema input processor provides several options to customize how schemas are interpreted into models. These options can be passed to the generator via the `processorOptions` parameter.
+
+### Available Options
+
+#### `interpretSingleEnumAsConst`
+**Type**: `boolean` (default: `false`)
+
+When enabled, a single enum value like `{enum: ['test']}` will be interpreted the same as `{const: 'test'}`. This reduces the number of enums being generated and uses constant values instead.
+
+**Example**:
+```typescript
+const generator = new TypeScriptGenerator({
+  processorOptions: {
+    jsonSchema: {
+      interpretSingleEnumAsConst: true
+    }
+  }
+});
+```
+
+See the [json-schema-single-enum-as-const example](../../examples/json-schema-single-enum-as-const) for a complete usage example.
+
+#### `propertyNameForAdditionalProperties`
+**Type**: `string` (default: `'additionalProperties'`)
+
+Changes which property name should be used to represent `additionalProperties` in JSON Schema. This is useful when you want to customize the generated property name for additional properties in your models.
+
+**Example**:
+```typescript
+const generator = new TypeScriptGenerator({
+  processorOptions: {
+    jsonSchema: {
+      propertyNameForAdditionalProperties: 'metadata'
+    }
+  }
+});
+```
+
+See the [json-schema-additional-properties-representation example](../../examples/json-schema-additional-properties-representation) for a complete usage example.
+
+#### `allowInheritance`
+**Type**: `boolean` (default: `false`)
+
+Enables support for inheritance in the generated models. When enabled, models can extend from other models based on the schema structure (such as `allOf` patterns).
+
+**Example**:
+```typescript
+const generator = new TypeScriptGenerator({
+  processorOptions: {
+    jsonSchema: {
+      allowInheritance: true
+    }
+  }
+});
+```
+
+See the [json-schema-allow-inheritance example](../../examples/json-schema-allow-inheritance) for a complete usage example.
+
+#### `disableCache`
+**Type**: `boolean` (default: `false`)
+
+Disables the seenSchemas cache in the Interpreter. This option should only be used in specific internal scenarios and generally should not be modified by end users.
+
+#### `ignoreAdditionalProperties`
+**Type**: `boolean` (default: `false`)
+
+For JSON Schema draft 7, `additionalProperties` are by default `true`, but this might create unintended properties in the models. Use this option to ignore default `additionalProperties` for models that have other properties defined with them.
+
+**Note**: ONLY use this option if you do not have control over your schema files. Instead, adapt your schemas to be more strict by setting `additionalProperties: false`.
+
+**Example**:
+```typescript
+const generator = new TypeScriptGenerator({
+  processorOptions: {
+    jsonSchema: {
+      ignoreAdditionalProperties: true
+    }
+  }
+});
+```
+
+See the [json-schema-ignore-additional-properties example](../../examples/json-schema-ignore-additional-properties) for a complete usage example.
+
+#### `ignoreAdditionalItems`
+**Type**: `boolean` (default: `false`)
+
+For JSON Schema draft 7, `additionalItems` are by default `true`, but this might create unintended types for arrays. Use this option to ignore default `additionalItems` for models as long as there are other types set for the array.
+
+**Note**: ONLY use this option if you do not have control over the schema files you use to generate models from. Instead, you should adapt your schemas to be more strict by setting `additionalItems: false`.
+
+**Example**:
+```typescript
+const generator = new TypeScriptGenerator({
+  processorOptions: {
+    jsonSchema: {
+      ignoreAdditionalItems: true
+    }
+  }
+});
+```
+
+See the [json-schema-ignore-additional-items example](../../examples/json-schema-ignore-additional-items) for a complete usage example.
+
+---
+
+For a comprehensive example demonstrating multiple processor options together, see the [json-schema-processor-options example](../../examples/json-schema-processor-options).
+
+## Interpretation of JSON Schema to CommonModel
 
 The library transforms JSON Schema from data validation rules to data definitions (`CommonModel`(s)). 
 

docs/migrations/version-4-to-5.md

@@ -0,0 +1,3 @@
+# Migration from v4 to v5
+
+There are no required changes to move from v4 to v5.