FlatFilers / Guides

Flatfile's Documentation
7 stars 20 forks source link

Add CLI actions #1131

Closed meritmalling closed 2 months ago

meritmalling commented 2 months ago

Summary by CodeRabbit

coderabbitai[bot] commented 2 months ago

Walkthrough

The recent documentation update revolves around enhancing the guidance for developing and deploying Listeners within the Flatfile ecosystem through the Flatfile CLI tool. It emphasizes crucial components like Listeners, Events, and Agents, providing a detailed table of CLI commands tailored for local development processes.

Changes

Files Change Summary
developer-tools/.../running-local.mdx Documentation updated for the Flatfile CLI, highlighting Listeners, Events, Agents, and CLI commands for local development and deployment.

Recent Review Details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between d1d33bb4d61b5344d1ec3a4b77b2043b35df663e and 6fee18dc07be918136a5012991756bdc8b94ebc8.
Files selected for processing (1) * developer-tools/developing/running-local.mdx (1 hunks)
Additional Context Used
LanguageTool (19)
developer-tools/developing/running-local.mdx (19)
Near line 10: Possible spelling mistake found. Context: ...et file="shared/dxpbanner.mdx" /> The Flatfile CLI provides a suite of tools to help y... --- Near line 10: Possible spelling mistake found. Context: ...Listeners](/orchestration/listeners) to Flatfile. Listeners are at the core of the Flat... --- Near line 12: Possible spelling mistake found. Context: ...file. Listeners are at the core of the Flatfile ecosystem, they are responsible for pic... --- Near line 20: Possible spelling mistake found. Context: ...e cloud. When developing with Flatfile, listeners can [deployed](../deploying)... --- Near line 20: Possible spelling mistake found. Context: ...steners can [deployed](../deploying) to Flatfile on every change, or they can run direct... --- Near line 21: Possible spelling mistake found. Context: ...y on your machine. When developing with Flatfile, listeners can [deployed](../deploying)... --- Near line 21: Possible spelling mistake found. Context: ...steners can [deployed](../deploying) to Flatfile on every change or they can run directl... --- Near line 21: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short). Context: ..../deploying) to Flatfile on every change or they can run directly on your machine. ... --- Near line 25: Possible spelling mistake found. Context: ...tly on your machine. ### Commands The Flatfile CLI provides the following commands: ... --- Near line 28: Possible typo: you repeated a whitespace Context: ...wing commands: | Command | Description | | ------- | -------------------------... --- Near line 30: Possible typo: you repeated a whitespace Context: ...p | Run your project as a local listener | | deploy | Deploy your project as a F... --- Near line 31: Possible typo: you repeated a whitespace Context: ...roject as a local listener | | deploy | Deploy your project as a Flatfile Agen... --- Near line 31: Possible spelling mistake found. Context: ... | | deploy | Deploy your project as a Flatfile Agent | | list | List deployed Agent... --- Near line 32: Possible typo: you repeated a whitespace Context: ...our project as a Flatfile Agent | | list | List deployed Agents in an environment... --- Near line 32: Possible typo: you repeated a whitespace Context: ...| List deployed Agents in an environment | | delete | Delete an Agent ... --- Near line 33: Possible typo: you repeated a whitespace Context: ...yed Agents in an environment | | delete | Delete an Agent ... --- Near line 33: Possible typo: you repeated a whitespace Context: ...vironment | | delete | Delete an Agent | ### Before you begin You can add a ... --- Near line 46: Possible spelling mistake found. Context: ...API_KEY=sk_123456 ``` ### Develop Run `npx flatfile develop` from terminal to laun... --- Near line 76: This verb may not be in the correct tense. Consider changing the tense to fit the context better. Context: ... the local listener. That's why the CLI is warning you when working in an environment that...
Additional comments not posted (6)
developer-tools/developing/running-local.mdx (6)
`9-13`: Introduction and basic information about the Flatfile CLI are well-written and clear. --- `15-17`: The note on Agents clearly explains their role and deployment. --- `28-34`: Remove extra whitespaces in the commands table for cleaner formatting. --- `6-38`: > :memo: **NOTE** > This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [35-46] The guidance on using the `.env` file to store the API key is practical and well-explained. --- Line range hint `46-76`: Detailed development instructions are comprehensive and provide valuable insights for developers. --- Line range hint `76-100`: The advice on using isolated environments is crucial and well-presented.
---
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.