Closed meritmalling closed 2 months ago
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.
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. |
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...
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.
Summary by CodeRabbit