version bump

.babelrc

@@ -0,0 +1,33 @@
+{
+  "presets": [
+    "@babel/preset-env"
+  ],
+  "plugins": [
+    "@babel/plugin-syntax-dynamic-import",
+    "@babel/plugin-syntax-import-meta",
+    "@babel/plugin-proposal-class-properties",
+    "@babel/plugin-proposal-json-strings",
+    [
+      "@babel/plugin-proposal-decorators",
+      {
+        "legacy": true
+      }
+    ],
+    "@babel/plugin-proposal-function-sent",
+    "@babel/plugin-proposal-export-namespace-from",
+    "@babel/plugin-proposal-numeric-separator",
+    "@babel/plugin-proposal-throw-expressions",
+    "@babel/plugin-proposal-export-default-from",
+    "@babel/plugin-proposal-logical-assignment-operators",
+    "@babel/plugin-proposal-optional-chaining",
+    [
+      "@babel/plugin-proposal-pipeline-operator",
+      {
+        "proposal": "minimal"
+      }
+    ],
+    "@babel/plugin-proposal-nullish-coalescing-operator",
+    "@babel/plugin-proposal-do-expressions",
+    "@babel/plugin-proposal-function-bind"
+  ]
+}

docs/ConfigResponse.md

@@ -6,7 +6,7 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **nitro** | [**ConfigResponseNitro**](ConfigResponseNitro.md) |  | [optional] 
 **pages** | **[String]** | A unique array of slugs is available for the entire site configuration, providing you with the flexibility to register specific routes for your application or compare a slug against this array. This comparison enables you to determine whether to return a \"404 Not Found\" exception or handle the request differently. By utilizing this array, you can easily manage and control the slugs used in your application, ensuring that only valid and registered routes are accessible. This approach helps maintain the integrity and security of your site's navigation, preventing users from accessing undefined or unauthorized pages. | [optional] 
-**containers** | [**{String: ConfigResponseContainersValue}**](ConfigResponseContainersValue.md) |  | [optional] 
+**containers** | [**{String: ConfigResponseContainersValue}**](ConfigResponseContainersValue.md) | This endpoint manages containers, which are essential for constructing navigation menus. Each navigation menu is housed within a distinct container. These containers are identified by two key attributes: a label and an identifier. The label describes the menu's purpose or position (e.g., \"Footer Nav\" or \"Main Nav\"), while the identifier is a slug-formatted text for easy reference (e.g., \"footer\"). Within each container, there is an \"items\" object. This object contains the actual page items that make up the menu's structure. | [optional] 
 **globals** | **Object** | The globals section serves as a crucial component in the overall structure of the code. It consists of an associative array that allows users to define their own unique keys, each of which contains an array of items representing data sourced from a Content Pool. This data is essential as it needs to be accessible throughout the entire scope of the website, ensuring its availability whenever required. By leveraging this globals section, developers can efficiently manage and access these globally significant data sets. | [optional] 
 
 

docs/EntityInterface.md

@@ -7,16 +7,16 @@ Name | Type | Description | Notes
 **version** | **Number** | A sequential index serves as a version identifier for an item, allowing for improved organization and extended functionality. By assigning a unique numerical value to each version, it becomes easier to track and manage different iterations of an item over time. | [optional] 
 **entityMetric** | [**EntityMetric**](EntityMetric.md) |  | [optional] 
 **entityUniqueId** | **String** | Unique ID | [optional] 
-**entityId** | **String** | An unique ID across the flyo sytem | [optional] 
+**entityId** | **Number** | An unique ID across the flyo sytem | [optional] 
 **entityImage** | **String** | For image manipulation please see https://dev.flyo.cloud/dev/infos/images.html | [optional] 
 **entitySlug** | **String** | The slug for the given item, this can be either unique or not, depending on the configuration of the entity definition schema. | [optional] 
 **entityTeaser** | **String** | The standard interface teaser resolved for the current entity | [optional] 
-**entityTimeEnd** | **String** | Unique ID | [optional] 
-**entityTimeStart** | **String** | If not defined, null is returned | [optional] 
+**entityTimeEnd** | **Number** | The shared entity interface time end attribute. If not defined, null or 0 is returned | [optional] 
+**entityTimeStart** | **Number** | The shared entity interface time start attribute. If not defined, null or 0 is returned | [optional] 
 **entityTitle** | **String** | The standard interface title resolved for the current entity | [optional] 
 **entityType** | **String** |  | [optional] 
 **entityTypeId** | **Number** | The Type-ID, alternatively referred to as the Entity-Definition-Schema ID, serves as a crucial identifier within the system. It uniquely distinguishes and categorizes the Entity-Definition-Schema. | [optional] 
-**updatedAt** | **String** |  | [optional] 
+**updatedAt** | **Number** | A Unix timestamp indicating when the entity has been updated last time in Flyo. | [optional] 
 **routes** | **{String: String}** |  | [optional] 
 
 

docs/EntityinterfaceInner.md

@@ -8,7 +8,7 @@ Name | Type | Description | Notes
 **entityTitle** | **String** | The standard interface title resolved for the current entity | [optional] 
 **entityTeaser** | **String** | The standard interface teaser resolved for the current entity | [optional] 
 **entitySlug** | **String** | The slug for the given item, this can be either unique or not, depending on the configuration of the entity definition schema. | [optional] 
-**entityTimeStart** | **String** | If not defined, null is returned | [optional] 
+**entityTimeStart** | **Number** | The shared entity interface time start attribute. If not defined, null or 0 is returned | [optional] 
 **entityType** | **String** |  | [optional] 
 **entityTypeId** | **Number** | The Type-ID, alternatively referred to as the Entity-Definition-Schema ID, serves as a crucial identifier within the system. It uniquely distinguishes and categorizes the Entity-Definition-Schema. | [optional] 
 **entityImage** | **String** | For image manipulation please see https://dev.flyo.cloud/dev/infos/images.html | [optional] 

docs/Page.md

@@ -4,16 +4,16 @@
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**id** | **Number** |  | [optional] 
+**id** | **Number** | The ID for the page | [optional] 
 **title** | **String** |  | [optional] 
 **href** | **String** | Returns the completed href tag. Internal links are appended with trailing slashes, such as `/about-me`, while email links are formatted with `mailto:hello@flyo.ch`. | [optional] 
 **slug** | **String** | The slug, in its current form, contains the full path of nested slugs and serves as the identifier for querying the respective page. | [optional] 
 **json** | [**[Block]**](Block.md) |  | [optional] 
-**depth** | **Number** |  | [optional] 
-**isHome** | **Number** |  | [optional] 
-**createdAt** | **Number** |  | [optional] 
-**updatedAt** | **Number** |  | [optional] 
-**isVisible** | **Number** |  | [optional] 
+**depth** | **Number** | The depth of the page in the tree structure | [optional] 
+**isHome** | **Number** | Determining whether the page is the homepage or not. | [optional] 
+**createdAt** | **Number** | A Unix timestamp indicating when the page was created. | [optional] 
+**updatedAt** | **Number** | A Unix timestamp indicating when the page was last updated. | [optional] 
+**isVisible** | **Number** | Determining whether the page is visible or not. | [optional] 
 **metaJson** | [**Meta**](Meta.md) |  | [optional] 
 **properties** | [**{String: PageProperty}**](PageProperty.md) |  | [optional] 
 **uid** | **String** | A unique identifier for the page | [optional] 

src/ApiClient.js

@@ -2,7 +2,7 @@
  * Flyo Nitro
  * This document provides a comprehensive overview of all the endpoints available for Flyo Nitro, a powerful platform designed to facilitate the development of websites. Flyo Nitro is built upon three strategic pillars that play a central role in website development:  + Config: The config component is responsible for loading all the necessary elements required for seamless navigation within the website layout. This includes crucial elements like the navigation menu or global content, such as the \"Locations\" section of an entity, which can be utilized in the footer across all pages. + Pages: Pages are evaluated based on their unique slug (path) and encompass all the content needed to populate a specific page. This includes various content elements, known as blocks, as well as meta information like \"og-descriptions.\" Additionally, pages can dynamically incorporate content from entities by employing mapping techniques. + Entity: Entities can be retrieved by utilizing a unique identifier, which can be configured within Flyo Nitro. Each entity provides comprehensive details in the form of fields, offering specific content tailored to a particular context.  Furthermore, it is important to distinguish between the **development** and **production** environments in Flyo Nitro. In the development environment, any changes made to data within the Flyo User Interface are immediately accessible, even without saving. This feature enables users to have a live preview of the changes during data entry. On the other hand, the production environment exclusively utilizes saved data, ensuring that only finalized content is displayed.  For more detailed documentation in German, please visit: dev.flyo.cloud
  *
- * The version of the OpenAPI document: 1.0.0-beta.164
+ * The version of the OpenAPI document: 1.0.0-beta.172
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -17,7 +17,7 @@ import querystring from "querystring";
 
 /**
 * @module ApiClient
-* @version 1.0.0-beta.164
+* @version 1.0.0-beta.172
 */
 
 /**
@@ -55,7 +55,7 @@ class ApiClient {
          * @default {}
          */
         this.defaultHeaders = {
-            'User-Agent': 'OpenAPI-Generator/1.0.0-beta.164/Javascript'
+            'User-Agent': 'OpenAPI-Generator/1.0.0-beta.172/Javascript'
         };
 
         /**

src/api/ConfigApi.js

@@ -2,7 +2,7 @@
  * Flyo Nitro
  * This document provides a comprehensive overview of all the endpoints available for Flyo Nitro, a powerful platform designed to facilitate the development of websites. Flyo Nitro is built upon three strategic pillars that play a central role in website development:  + Config: The config component is responsible for loading all the necessary elements required for seamless navigation within the website layout. This includes crucial elements like the navigation menu or global content, such as the \"Locations\" section of an entity, which can be utilized in the footer across all pages. + Pages: Pages are evaluated based on their unique slug (path) and encompass all the content needed to populate a specific page. This includes various content elements, known as blocks, as well as meta information like \"og-descriptions.\" Additionally, pages can dynamically incorporate content from entities by employing mapping techniques. + Entity: Entities can be retrieved by utilizing a unique identifier, which can be configured within Flyo Nitro. Each entity provides comprehensive details in the form of fields, offering specific content tailored to a particular context.  Furthermore, it is important to distinguish between the **development** and **production** environments in Flyo Nitro. In the development environment, any changes made to data within the Flyo User Interface are immediately accessible, even without saving. This feature enables users to have a live preview of the changes during data entry. On the other hand, the production environment exclusively utilizes saved data, ensuring that only finalized content is displayed.  For more detailed documentation in German, please visit: dev.flyo.cloud
  *
- * The version of the OpenAPI document: 1.0.0-beta.164
+ * The version of the OpenAPI document: 1.0.0-beta.172
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -18,7 +18,7 @@ import ConfigResponse from '../model/ConfigResponse';
 /**
 * Config service.
 * @module api/ConfigApi
-* @version 1.0.0-beta.164
+* @version 1.0.0-beta.172
 */
 export default class ConfigApi {
 

src/api/EntitiesApi.js

@@ -2,7 +2,7 @@
  * Flyo Nitro
  * This document provides a comprehensive overview of all the endpoints available for Flyo Nitro, a powerful platform designed to facilitate the development of websites. Flyo Nitro is built upon three strategic pillars that play a central role in website development:  + Config: The config component is responsible for loading all the necessary elements required for seamless navigation within the website layout. This includes crucial elements like the navigation menu or global content, such as the \"Locations\" section of an entity, which can be utilized in the footer across all pages. + Pages: Pages are evaluated based on their unique slug (path) and encompass all the content needed to populate a specific page. This includes various content elements, known as blocks, as well as meta information like \"og-descriptions.\" Additionally, pages can dynamically incorporate content from entities by employing mapping techniques. + Entity: Entities can be retrieved by utilizing a unique identifier, which can be configured within Flyo Nitro. Each entity provides comprehensive details in the form of fields, offering specific content tailored to a particular context.  Furthermore, it is important to distinguish between the **development** and **production** environments in Flyo Nitro. In the development environment, any changes made to data within the Flyo User Interface are immediately accessible, even without saving. This feature enables users to have a live preview of the changes during data entry. On the other hand, the production environment exclusively utilizes saved data, ensuring that only finalized content is displayed.  For more detailed documentation in German, please visit: dev.flyo.cloud
  *
- * The version of the OpenAPI document: 1.0.0-beta.164
+ * The version of the OpenAPI document: 1.0.0-beta.172
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -18,7 +18,7 @@ import Entity from '../model/Entity';
 /**
 * Entities service.
 * @module api/EntitiesApi
-* @version 1.0.0-beta.164
+* @version 1.0.0-beta.172
 */
 export default class EntitiesApi {
 

src/api/PagesApi.js

@@ -2,7 +2,7 @@
  * Flyo Nitro
  * This document provides a comprehensive overview of all the endpoints available for Flyo Nitro, a powerful platform designed to facilitate the development of websites. Flyo Nitro is built upon three strategic pillars that play a central role in website development:  + Config: The config component is responsible for loading all the necessary elements required for seamless navigation within the website layout. This includes crucial elements like the navigation menu or global content, such as the \"Locations\" section of an entity, which can be utilized in the footer across all pages. + Pages: Pages are evaluated based on their unique slug (path) and encompass all the content needed to populate a specific page. This includes various content elements, known as blocks, as well as meta information like \"og-descriptions.\" Additionally, pages can dynamically incorporate content from entities by employing mapping techniques. + Entity: Entities can be retrieved by utilizing a unique identifier, which can be configured within Flyo Nitro. Each entity provides comprehensive details in the form of fields, offering specific content tailored to a particular context.  Furthermore, it is important to distinguish between the **development** and **production** environments in Flyo Nitro. In the development environment, any changes made to data within the Flyo User Interface are immediately accessible, even without saving. This feature enables users to have a live preview of the changes during data entry. On the other hand, the production environment exclusively utilizes saved data, ensuring that only finalized content is displayed.  For more detailed documentation in German, please visit: dev.flyo.cloud
  *
- * The version of the OpenAPI document: 1.0.0-beta.164
+ * The version of the OpenAPI document: 1.0.0-beta.172
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -18,7 +18,7 @@ import Page from '../model/Page';
 /**
 * Pages service.
 * @module api/PagesApi
-* @version 1.0.0-beta.164
+* @version 1.0.0-beta.172
 */
 export default class PagesApi {
 

src/api/SearchApi.js

@@ -2,7 +2,7 @@
  * Flyo Nitro
  * This document provides a comprehensive overview of all the endpoints available for Flyo Nitro, a powerful platform designed to facilitate the development of websites. Flyo Nitro is built upon three strategic pillars that play a central role in website development:  + Config: The config component is responsible for loading all the necessary elements required for seamless navigation within the website layout. This includes crucial elements like the navigation menu or global content, such as the \"Locations\" section of an entity, which can be utilized in the footer across all pages. + Pages: Pages are evaluated based on their unique slug (path) and encompass all the content needed to populate a specific page. This includes various content elements, known as blocks, as well as meta information like \"og-descriptions.\" Additionally, pages can dynamically incorporate content from entities by employing mapping techniques. + Entity: Entities can be retrieved by utilizing a unique identifier, which can be configured within Flyo Nitro. Each entity provides comprehensive details in the form of fields, offering specific content tailored to a particular context.  Furthermore, it is important to distinguish between the **development** and **production** environments in Flyo Nitro. In the development environment, any changes made to data within the Flyo User Interface are immediately accessible, even without saving. This feature enables users to have a live preview of the changes during data entry. On the other hand, the production environment exclusively utilizes saved data, ensuring that only finalized content is displayed.  For more detailed documentation in German, please visit: dev.flyo.cloud
  *
- * The version of the OpenAPI document: 1.0.0-beta.164
+ * The version of the OpenAPI document: 1.0.0-beta.172
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -18,7 +18,7 @@ import EntityinterfaceInner from '../model/EntityinterfaceInner';
 /**
 * Search service.
 * @module api/SearchApi
-* @version 1.0.0-beta.164
+* @version 1.0.0-beta.172
 */
 export default class SearchApi {