bump to 1.0.0-beta.150

.openapi-generator/FILES

@@ -19,12 +19,15 @@ docs/PagesApi.md
 docs/PagesInner.md
 docs/SearchApi.md
 docs/SitemapApi.md
+docs/VersionApi.md
+docs/VersionResponse.md
 src/ApiClient.js
 src/api/ConfigApi.js
 src/api/EntitiesApi.js
 src/api/PagesApi.js
 src/api/SearchApi.js
 src/api/SitemapApi.js
+src/api/VersionApi.js
 src/index.js
 src/model/Block.js
 src/model/BlockSlots.js
@@ -40,3 +43,4 @@ src/model/Page.js
 src/model/PageBreadcrumbInner.js
 src/model/PageProperty.js
 src/model/PagesInner.js
+src/model/VersionResponse.js

docs/ConfigResponseNitro.md

@@ -6,8 +6,8 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **domain** | **String** |  | [optional] 
 **slug** | **String** |  | [optional] 
-**version** | **Number** | Whenever Flyo generates new data, the version number will be incremented accordingly. This version number serves as a valuable tool for caching storage of your application. | [optional] 
-**updatedAt** | **Number** |  | [optional] 
+**version** | **Number** | Whenever Flyo generates new data, the version number will be appropriately incremented. If this value is employed for caching, it will undergo less frequent purging in comparison to the `updated_at` value, thus extending its longevity. (last longer) | [optional] 
+**updatedAt** | **Number** | A Unix timestamp indicating when the Nitro was last updated. This timestamp does not correlate with the version number. If this value is utilized for caching purposes, it will experience more frequent purges compared to the version number, leading to shorter caching intervals. (last shorter) | [optional] 
 **language** | **String** |  | [optional] 
 
 

docs/Page.md

@@ -6,7 +6,8 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **id** | **Number** |  | [optional] 
 **title** | **String** |  | [optional] 
-**slug** | **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] 

docs/PagesInner.md

@@ -7,8 +7,8 @@ Name | Type | Description | Notes
 **type** | **String** | The `page` type is the default behavior for a webpage, but it can also be assigned different types to suit specific purposes. In addition to the default content type, there are several other types available, including `email`, `file`, `url` and `tel`. By specifying these types, you can customize the behavior and functionality of your page to better align with your requirements. | [optional] 
 **target** | **String** | can be either _self (which is default) or _blank | [optional] 
 **label** | **String** |  | [optional] 
-**href** | **String** |  | [optional] 
-**path** | **String** | A path always starts with a trailing slash | [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] 
 **properties** | **{String: Object}** |  | [optional] 
 **children** | [**[PagesInner]**](PagesInner.md) | Represents a comprehensive collection of pages within the specified container. These pages are organized in a nested tree structure, where each page can have child pages associated with it. These child pages are conveniently stored within the children property of their respective parent page. | [optional] 
 

docs/VersionApi.md

@@ -0,0 +1,55 @@
+# Nitro.VersionApi
+
+All URIs are relative to *https://api.flyo.cloud/nitro/v1*
+
+Method | HTTP request | Description
+------------- | ------------- | -------------
+[**version**](VersionApi.md#version) | **GET** /version | Get Version Information
+
+
+
+## version
+
+> VersionResponse version()
+
+Get Version Information
+
+The Version API endpoint offers a highly efficient solution for evaluating the current caching status of your application's caching mechanism. This functionality allows you to cache the entire application configuration and page responses indefinitely. However, utilizing this endpoint enables you to assess the validity of the cache by sending a request to determine its current status. This caching endpoint is specifically designed for optimal performance when compared to the configuration endpoint, which requires more thorough evaluation and encompasses a substantial response body.
+
+### Example
+
+```javascript
+import Nitro from 'nitro';
+let defaultClient = Nitro.ApiClient.instance;
+// Configure API key authorization: ApiToken
+let ApiToken = defaultClient.authentications['ApiToken'];
+ApiToken.apiKey = 'YOUR API KEY';
+// Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
+//ApiToken.apiKeyPrefix = 'Token';
+
+let apiInstance = new Nitro.VersionApi();
+apiInstance.version().then((data) => {
+  console.log('API called successfully. Returned data: ' + data);
+}, (error) => {
+  console.error(error);
+});
+
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+[**VersionResponse**](VersionResponse.md)
+
+### Authorization
+
+[ApiToken](../README.md#ApiToken)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+

docs/VersionResponse.md

@@ -0,0 +1,10 @@
+# Nitro.VersionResponse
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**version** | **Number** | Whenever Flyo generates new data, the version number will be appropriately incremented. If this value is employed for caching, it will undergo less frequent purging in comparison to the `updated_at` value, thus extending its longevity. (last longer) | [optional] 
+**updatedAt** | **Number** | A Unix timestamp indicating when the Nitro was last updated. This timestamp does not correlate with the version number. If this value is utilized for caching purposes, it will experience more frequent purges compared to the version number, leading to shorter caching intervals. (last shorter) | [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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * 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.145
+* @version 1.0.0-beta.150
 */
 
 /**
@@ -55,7 +55,7 @@ class ApiClient {
          * @default {}
          */
         this.defaultHeaders = {
-            'User-Agent': 'OpenAPI-Generator/1.0.0-beta.145/Javascript'
+            'User-Agent': 'OpenAPI-Generator/1.0.0-beta.150/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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * 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.145
+* @version 1.0.0-beta.150
 */
 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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * 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.145
+* @version 1.0.0-beta.150
 */
 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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * 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.145
+* @version 1.0.0-beta.150
 */
 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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * 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.145
+* @version 1.0.0-beta.150
 */
 export default class SearchApi {
 

src/api/SitemapApi.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.145
+ * The version of the OpenAPI document: 1.0.0-beta.150
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -18,7 +18,7 @@ import EntityinterfaceInner from '../model/EntityinterfaceInner';
 /**
 * Sitemap service.
 * @module api/SitemapApi
-* @version 1.0.0-beta.145
+* @version 1.0.0-beta.150
 */
 export default class SitemapApi {