🚩GitHub Issues:
- Update heading level for GitHub Issues section to match the document structure
Issue labels:
- Update heading level for Issue labels section to match the document structure
Local development:
- Update heading level for Local development section to match the document structure
Run locally:
- Update heading level for Run locally section to match the document structure
- Add instructions for installing dependencies and starting the development server for the backend
- Add instructions for installing dependencies and starting the development server for the frontend
Docker compose:
- Update heading level for Docker compose section to match the document structure
- Add instructions for running the backend and frontend using Docker compose
Documentation:
- Update heading level for Documentation section to match the document structure
- Add instructions for running the documentation locally using Docusaurus
- Update the available URL for the documentation
Create a Pull Request:
- Add a closing statement with instructions to create a Pull Request to the `main` branch
The change clarifies that using a `Document` as input in the `FlowRunner` class is a straightforward way to pass text data in Langflow, specifically because it can be connected to many loaders. It also mentions that generally, a flow expects a string or a dictionary as input. Additionally, it updates the explanation of extracting the content of a document using the `page_content` attribute, which is a string.
The commit adds an explanation about using a `Document` as input in the `FlowRunner` class. It clarifies that using a `Document` is a straightforward way to pass text data in Langflow. Typically, a flow expects a string or a dictionary as input, and if a dictionary is used, it should be built according to the needs of the specific flow. The commit also mentions that the content of a document can be extracted using the `page_content` property and passed as an argument to the selected flow.
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): improve readability and formatting in the CustomComponent class documentation
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): update CustomComponent class documentation with additional methods and descriptions
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): update CustomComponent class documentation with corrected method names and descriptions
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
ℹ️ The example code demonstrates how to create a custom component called "Flow Runner" that runs other flows using a document as input. The code includes the implementation of the `build_config` and `build` methods.
✨ feat(flow-runner.mdx): add example code for a Flow Runner custom component to provide a practical example for users to follow
🐛 fix(flow-runner.mdx): remove unnecessary focus annotations in code snippets
✨ feat(flow-runner.mdx): add support for getting flow by name instead of id in build method
✨ feat(flow-runner.mdx): add caution about unique flow names in version 0.4.0
✨ feat(flow-runner.mdx): add support for passing document parameter in build method
🐛 fix(flow-runner.mdx): remove redundant Optional type hint for document parameter in build method
🐛 fix(flow-runner.mdx): remove empty line at the end of the file
✨ feat(directory_reader.py): add methods to check if a specific type hint is imported and used in function arguments
✨ feat(directory_reader.py): add method to check if a type hint is used but not imported in the code
✨ feat(directory_reader.py): add check for usage of 'Optional' type hint without importing it in the process_file method
fix(extraSidebarComponent): update key prop in ShadTooltip component to use unique value
fix(extraSidebarComponent): update draggable attribute in component div to be disabled if there is an error
feat(api): add error property to APIClassType to indicate if there is an error in the component
🐛 fix(custom.mdx): add missing punctuation in the field descriptions
✨ feat(custom.mdx): add clarification to the field descriptions and provide examples for some fields
📝 docs(custom.mdx): add missing punctuation in the method description
🐛 fix(custom.mdx): add comment to clarify the purpose of the line
