\n Use the source control and CI tools you love<\/h4>\n
\n
Use git to manage your configuration, review and merge changes, and run development versions of your app before deploying to production. Use the CI processes that your team are familiar with to manage your apps.<\/p>\n <\/li>\n <\/ul>\n"}
-{"prompt":"The given YAML file is a configuration file for the `_type` operator in Lowdefy. It provides information about how to use the `_type` operator, which performs a type test on an object and returns true if the object is of the specified type. Here is a breakdown of the YAML file:\n\n- `_ref`: This is a reference to a template file that provides the content for the operator documentation.\n - `path: templates\/operators.yaml.njk`: This specifies the path to the template file that contains the documentation content.\n - `transformer: templates\/operatorsMethodTransformer.js`: This specifies the transformer file that will be used to process the template and generate the final documentation.\n - `vars`: This section defines the variables that will be used in the template file to generate the documentation content.\n - `pageId: _type`: This is the ID of the operator, which is `_type`.\n - `pageTitle: _type`: This is the title of the operator, which is `_type`.\n - `filePath: operators\/_type.yaml`: This is the file path where the operator configuration is stored.\n - `build: true`: This indicates that the operator documentation should be built.\n - `types: |`: This is a multiline string that defines the types and arguments supported by the `_type` operator.\n - `description: |`: This is a multiline string that provides a description of the `_type` operator and its functionality.\n - `arguments: |`: This is a multiline string that describes the arguments that can be used with the `_type` operator.\n - `examples: |`: This is a multiline string that provides examples of how to use the `_type` operator in different scenarios.\n\nThe content of the template file will be processed by the transformer to generate the final documentation for the `_type` operator. The documentation includes information about the supported types, arguments, description, and examples of usage.\n\nOverall, this YAML file provides the configuration for generating the documentation for the `_type` operator in Lowdefy. It includes information about the supported types, arguments, and provides examples of how to use the operator in different scenarios.","completion":"# Copyright 2020-2023 Lowdefy, Inc\n\n# Licensed under the Apache License, Version 2.0 (the \"License\");\n# you may not use this file except in compliance with the License.\n# You may obtain a copy of the License at\n\n# http:\/\/www.apache.org\/licenses\/LICENSE-2.0\n\n# Unless required by applicable law or agreed to in writing, software\n# distributed under the License is distributed on an \"AS IS\" BASIS,\n# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n# See the License for the specific language governing permissions and\n# limitations under the License.\n\n_ref:\n path: templates\/operators.yaml.njk\n transformer: templates\/operatorsMethodTransformer.js\n vars:\n pageId: _type\n pageTitle: _type\n filePath: operators\/_type.yaml\n build: true\n types: |\n ```\n (type: enum): boolean\n (arguments: {\n type: string,\n on?: any,\n key?: string\n }): boolean\n ```\n description: |\n The `_type` operator performs a type test on an object, and returns true if the object is of the specified type.\n\n The regex operator has shorthand argument definitions that can be used on web client.\n arguments: |\n ###### object\n - `type: enum`: __Required__ - The type to test. Can be one of:\n - `string`\n - `array`\n - `date`\n - `object`\n - `boolean`\n - `number`\n - `integer`\n - `null`\n - `undefined`\n - `none` (`null` or `undefined`)\n - `primitive` (`undefined`, `null`, `string`, `number`, `boolean`, or `date`)\n - `on: any`: The value to test. One of `on` or `key` must be specified unless the operator is used in an input block.\n - `key: string`: The key of a value in `state` to test. One of `on` or `key` must be specified unless the operator is used in an input block.\n\n ###### string\n The type to test. The string shorthand can only be used in an input block, and the tested value will be the block's value.\n examples: |\n ###### Check if a value is a number:\n ```yaml\n _type:\n type: number\n on:\n _state: input\n ```\n Returns: `true` if a number.\n\n ###### Using the key of the value in `state`:\n ```yaml\n _type:\n type: number\n key: input\n ```\n Returns: `true` if a number.\n\n ###### Using the value of the block in which the operator is evaluated:\n ```yaml\n id: input\n type: TextInput\n validate:\n - message: This field id required.\n status: error\n pass:\n _not:\n _type: none\n ```\n Returns: `true` if the input is none.\n\n ###### Test if an id in the `urlQuery` is undefined or null:\n ```yaml\n _type:\n type: none\n on:\n _url_query: id\n ```\n Returns: `true` if the id is none,\n"}
-{"prompt":"The name of the YAML file is \"DangerousMarkdown.yaml\". This file defines a block called \"DangerousMarkdown\" in the Lowdefy framework. The block is used to render markdown content that can include HTML elements. It uses DOMPurify to sanitize the markdown content before converting it to HTML. The YAML file includes configuration for the block, such as its category, schema, description, initial property values, and examples. The examples demonstrate how the block can be used to render markdown content with HTML elements, such as embedding an iframe in the markdown. The block provides the ability to customize the sanitization options for added security. However, it is advised to only render hardcoded or trusted markdown and HTML content, and not user input, due to security considerations.","completion":"# Copyright 2020-2023 Lowdefy, Inc\n\n# Licensed under the Apache License, Version 2.0 (the \"License\");\n# you may not use this file except in compliance with the License.\n# You may obtain a copy of the License at\n\n# http:\/\/www.apache.org\/licenses\/LICENSE-2.0\n\n# Unless required by applicable law or agreed to in writing, software\n# distributed under the License is distributed on an \"AS IS\" BASIS,\n# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n# See the License for the specific language governing permissions and\n# limitations under the License.\n\n_ref:\n path: templates\/blocks\/template.yaml.njk\n vars:\n block_type: DangerousMarkdown\n category: display\n schema: ..\/plugins\/blocks\/blocks-markdown\/src\/blocks\/DangerousMarkdown\/schema.json\n filePath: blocks\/display\/DangerousMarkdown.yaml\n init_property_values:\n content: |\n ## Some Html content:\n\n
A simple white title box<\/h4><\/div>\n\n description_content: |\n Render markdown content which can include HTML elements. If the markdown content does not need to render HTML, use the [Markdown](\/Markdown) or [MarkdownWithCode](\/MarkdownWithCode) blocks instead. Specify what HTML element to allow or remove by changing the default modifying the [DOMPurify's options](https:\/\/github.com\/cure53\/DOMPurify#can-i-configure-dompurify).\n\n > The DangerousMarkdown block sanitizes the markdown content using [DOMPurify's](https:\/\/github.com\/cure53\/DOMPurify) before converting the markdown to HTML. DangerousMarkdown provides the ability to customize the sanitization options. This comes with some security considerations, please consider [DOMPurify's Security Goals and Threat Model](https:\/\/github.com\/cure53\/DOMPurify\/wiki\/Security-Goals-&-Threat-Model) for more details regarding the security impact of using the DangerousMarkdown block.\n >\n > In short, it is strongly advised to never render any user input DangerousMarkdown content, only render hardcoded or trusted markdown and HTML content.\n\n examples:\n - title: DangerousMarkdown headings\n block:\n id: iframes_example\n type: DangerousMarkdown\n properties:\n DOMPurifyOptions\":\n ADD_TAGS\":\n - iframe\n content: |\n # Markdown with an iframe:\n
