Merge pull request #471 from lowdefy/docs-descriptions-fix

fix(blocks-antd): Fix Descriptions bordered property default value

packages/blocks/blocksAntd/src/blocks/Descriptions/Descriptions.json

@@ -13,7 +13,7 @@
       "properties": {
         "bordered": {
           "type": "boolean",
-          "default": true,
+          "default": false,
           "description": "Render items in a table."
         },
         "colon": {
@@ -22,6 +22,7 @@
           "description": "Include a colon in item labels."
         },
         "column": {
+          "default": 3,
           "oneOf": [
             {
               "type": "number",

packages/docs/blocks/display/Descriptions.yaml

@@ -22,7 +22,6 @@ _ref:
     init_state_values:
       __type_block.properties.column: number
       __type_block.properties.items: object[]
-      __number_block.properties.column: 2
       __object_arr_block.properties.items:
         - label: Item One
           value: 1
@@ -32,6 +31,7 @@ _ref:
           value: 3
         - label: Item Four
           value: 4
+          span: 3
 
     description_content: |
       Display multiple read-only fields in groups. Commonly used to display a detailed set of data.
@@ -41,9 +41,9 @@ _ref:
         block:
           id: object_example
           type: Descriptions
-          properties: 
-            items: 
-              Location: South Africa 
+          properties:
+            bordered: true
+            items:
+              Location: South Africa
               Temperature: 22
               Date: 2021-02-02
-      

packages/docs/concepts/lowdefy-schema.yaml

@@ -197,6 +197,10 @@ _ref:
 
             Templating is used extensively to create the Lowdefy docs (these docs are a Lowdefy app). You can look at how they are used [here](https://github.com/lowdefy/lowdefy/tree/main/packages/docs).
 
+            ## JSON instead of YAML
+
+            Since you can reference JSON files, you can build your app using JSON instead of YAML files. The `lowdefy.yaml` file needs to be a YAML file, but all other configuration can be in referenced JSON files. It also makes sense to use JSON instead of YAML if you are generating configuration using code.
+
             # Lowdefy versions and version updates
 
             Lowdefy is versioned using semantic versioning, with a three part version number, with the form `major.minor.patch`. Lowdefy is in the early stages of development and under active development, with new versions published on a regular basis.

packages/docs/introduction.yaml

@@ -52,6 +52,8 @@ _ref:
               - App config is just data, thus you can even develop scripts to create and manage your apps.
               - YAML files work with your favorite developer and source control tools.
 
+            > If you aren't a fan of YAML, you can also build your app using JSON files.
+
             ### Work with your data where it is stored
 
             Lowdefy apps can connect to multiple data bases, APIs and apps. Day to day business requires people working with data which is stored in a variety of different data bases and applications.

packages/docs/operators/_ref.yaml

@@ -47,7 +47,7 @@ _ref:
 
       ###### Transformer
 
-      A transformer is a Javascript function that receives the result of the `_ref` operator, and it's `vars`. The value returned by this function will be included in the configuration as the final result of the `_ref` operator. The `transformer` argument should be the file path (relative to the root of the project) to a Javascript file that exports a transformer function. For example:
+      A transformer is a Javascript function that receives the result of the `_ref` operator, and its `vars`. The value returned by this function will be included in the configuration as the final result of the `_ref` operator. The `transformer` argument should be the file path (relative to the root of the project) to a Javascript file that exports a transformer function. For example:
 
       ```js
       // transformer.js