You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: desktop/src-tauri/src/types/generated/flowfile.rs
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2182,15 +2182,15 @@ impl ::std::default::Default for ExecutableVerb {
2182
2182
ExecutableVerb::Exec
2183
2183
}
2184
2184
}
2185
-
#[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"]
2185
+
#[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 = " \"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\","]
2193
+
#[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\","]
Copy file name to clipboardExpand all lines: docs/quickstart.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ workspace's configurations. For more information on workspaces see the [workspac
22
22
23
23
**Create an executable**
24
24
25
-
Executables are the core of flow. Each executable is driven by its definition within a flow file (`*.flow`).
25
+
Executables are the core of flow. Each executable is driven by its definition within a flow file (`*.flow`, `*.flow.yaml`, or `*.flow.yml`).
26
26
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).
27
27
28
28
To get started, create a new flow file in the workspace directory.
"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",
5
+
"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",
Copy file name to clipboardExpand all lines: docs/types/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,4 +16,4 @@ You can add the following comment to the top of your flow files to enable this:
16
16
17
17
See the [schemas directory on GitHub](https://github.com/jahvon/flow/tree/main/docs/schemas) for all available schemas.
18
18
19
-
Note: If using the flow file schema, you will need to make sure your IDE is configured to treat `*.flow` files as YAML files.
19
+
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.
0 commit comments