generate and update docs

Author: jahvon

desktop/src-tauri/src/types/generated/flowfile.rs

@@ -2182,15 +2182,15 @@ impl ::std::default::Default for ExecutableVerb {
         ExecutableVerb::Exec
     }
 }
-#[doc = "Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered \nby the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).\nA workspace can have multiple flow files located anywhere in the workspace directory\n"]
+#[doc = "Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml` \nin order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata \n(namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory\n"]
 #[doc = r""]
 #[doc = r" <details><summary>JSON schema</summary>"]
 #[doc = r""]
 #[doc = r" ```json"]
 #[doc = "{"]
 #[doc = "  \"$id\": \"https://flowexec.io/schemas/flowfile_schema.json\","]
 #[doc = "  \"title\": \"FlowFile\","]
-#[doc = "  \"description\": \"Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered \\nby the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).\\nA workspace can have multiple flow files located anywhere in the workspace directory\\n\","]
+#[doc = "  \"description\": \"Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml` \\nin order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata \\n(namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory\\n\","]
 #[doc = "  \"type\": \"object\","]
 #[doc = "  \"properties\": {"]
 #[doc = "    \"description\": {"]

desktop/src/types/generated/flowfile.ts

@@ -44,9 +44,9 @@ export type CommonVisibility = 'public' | 'private' | 'internal' | 'hidden';
 export type FromFile = string[];
 
 /**
- * Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered
- * by the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).
- * A workspace can have multiple flow files located anywhere in the workspace directory
+ * Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml`
+ * in order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata
+ * (namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory
  *
  */
 export interface FlowFile {

docs/guide/executable.md

@@ -71,7 +71,7 @@ flow build my-project/
 ## Flowfile
 
 The flowfile is the primary configuration file that defines what an executable should do. The file is written in YAML but
-should have a `.flow` extension.
+should have a `.flow`, `.flow.yaml`, or `.flow.yml` extension.
 
 The [flow sync](../cli/flow_sync.md) command is used to trigger a discovery of executables within workspaces. This 
 command should be run whenever an executable is created, moved, or deleted from a flowfile.

docs/quickstart.md

@@ -22,7 +22,7 @@ workspace's configurations. For more information on workspaces see the [workspac
 
 **Create an executable**
 
-Executables are the core of flow. Each executable is driven by its definition within a flow file (`*.flow`).
+Executables are the core of flow. Each executable is driven by its definition within a flow file (`*.flow`, `*.flow.yaml`, or `*.flow.yml`).
 There are several types of executables that can be defined. For more information on executables and the flow file, see the [executable guide](guide/executable.md).
 
 To get started, create a new flow file in the workspace directory.

docs/schemas/flowfile_schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://flowexec.io/schemas/flowfile_schema.json",
   "title": "FlowFile",
-  "description": "Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered \nby the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).\nA workspace can have multiple flow files located anywhere in the workspace directory\n",
+  "description": "Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml` \nin order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata \n(namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory\n",
   "type": "object",
   "definitions": {
     "CommonAliases": {

docs/types/README.md

@@ -16,4 +16,4 @@ You can add the following comment to the top of your flow files to enable this:
 
 See the [schemas directory on GitHub](https://github.com/jahvon/flow/tree/main/docs/schemas) for all available schemas.
 
-Note: If using the flow file schema, you will need to make sure your IDE is configured to treat `*.flow` files as YAML files.
+Note: If using the flow file schema, you will need to make sure your IDE is configured to treat `*.flow`, `*.flow.yaml`, and `*.flow.yml` files as YAML files.

docs/types/flowfile.md

@@ -2,9 +2,9 @@
 
 # FlowFile
 
-Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered 
-by the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).
-A workspace can have multiple flow files located anywhere in the workspace directory
+Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml` 
+in order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata 
+(namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory
 
 
 ## Properties

types/executable/flowfile.gen.go

@@ -3,9 +3,9 @@ $id: "https://raw.githubusercontent.com/jahvon/flow/HEAD/types/executable/flowfi
 
 title: FlowFile
 description: |
-  Configuration for a group of Flow CLI executables. The file must have the extension `.flow` in order to be discovered 
-  by the CLI. It's configuration is used to define a group of executables with shared metadata (namespace, tags, etc).
-  A workspace can have multiple flow files located anywhere in the workspace directory
+  Configuration for a group of Flow CLI executables. The file must have the extension `.flow`, `.flow.yaml`, or `.flow.yml` 
+  in order to be discovered by the CLI. It's configuration is used to define a group of executables with shared metadata 
+  (namespace, tags, etc). A workspace can have multiple flow files located anywhere in the workspace directory
 
 definitions:
   FromFile:

types/executable/flowfile_schema.yaml

@@ -16,6 +16,7 @@ import (
 
 const FlowFileTemplateExt = ".flow.tmpl"
 
+//nolint:lll
 var FlowFileTemplateExtRegex = regexp.MustCompile(fmt.Sprintf(`%s(\.yaml|\.yml)?`, regexp.QuoteMeta(FlowFileTemplateExt)))
 
 type TemplateList []*Template