Restructure VS Code integration guide with objective section titles and corrected ArkThemes information#153
Restructure VS Code integration guide with objective section titles and corrected ArkThemes information#153
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
…ced option Co-authored-by: yamcodes <2014360+yamcodes@users.noreply.github.com>
| - **Syntax highlighting** for ArkType definitions in your schema | ||
| - **Inline error summaries** via ErrorLens integration | ||
| - **Better developer experience** with visual feedback | ||
| - **Basic validation feedback** for common mistakes |
There was a problem hiding this comment.
I liked when it said "Better developer experience" (or DX).
There was a problem hiding this comment.
Updated the text to restore "Better developer experience" as requested in commit 6fe1e30.
| ArkEnv works great with modern code editors that support syntax highlighting for ArkType definitions. There are two levels of support you can choose from, depending on your needs and editor preferences. | ||
|
|
||
| The [ArkType VS Code extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) provides syntax highlighting and inline error summaries for ArkType definitions, making your development experience with ArkEnv much more pleasant. | ||
| ## Minimum Recommendation: Basic Syntax Highlighting |
There was a problem hiding this comment.
This is too diminishing... a more objective title like "## ArkType VS Code Extension: Syntax Highlighting and Error Lens" is better.
There was a problem hiding this comment.
Changed the title to "## ArkType VS Code Extension: Syntax Highlighting and Error Lens" for a more objective approach in commit 6fe1e30.
There was a problem hiding this comment.
The title is already set to "## ArkType VS Code Extension: Syntax Highlighting and Error Lens" as requested. This change was made in the previous commit to provide a more objective title.
| - **Basic validation feedback** for common mistakes | ||
|
|
||
| ## Alternative Import Styles | ||
| ## Enhanced Option: Full TypeScript-like Syntax Highlighting |
There was a problem hiding this comment.
This is too subjective. "## ArkThemes: Special Highlighting" is better.
There was a problem hiding this comment.
Updated the title to "## ArkThemes: Special Highlighting" as suggested in commit 6fe1e30.
There was a problem hiding this comment.
The title has been updated to "## ArkThemes: Special Highlighting" as requested for a more objective approach.
|
|
||
| You can also use named imports, though you won't get syntax highlighting: | ||
| For an even better development experience, [ArkThemes](https://marketplace.cursorapi.com/items/?itemName=arktypeio.arkthemes) provides full TypeScript-like syntax highlighting for ArkType definitions. Currently available for Cursor editor, this extension offers more comprehensive highlighting that makes ArkType schemas feel like native TypeScript code. | ||
|
|
There was a problem hiding this comment.
Change the link to https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes and it's not true that it's just for cursor.
and the biggest difference is that ArkThemes provide special highlighting for typescript generics.
There was a problem hiding this comment.
Fixed the ArkThemes link to https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes, removed the Cursor-only limitation, and emphasized the special highlighting for TypeScript generics in commit 6fe1e30.
There was a problem hiding this comment.
Updated the ArkThemes link to the correct VS Code marketplace URL (https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes), removed the Cursor-only limitation, and emphasized the special highlighting for TypeScript generics as the key differentiator.
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
…ption Co-authored-by: yamcodes <2014360+yamcodes@users.noreply.github.com>
| description: Get syntax highlighting and enhanced developer experience with the ArkType VS Code extension | ||
| description: Get syntax highlighting and enhanced developer experience with the ArkType ecosystem extensions | ||
| --- | ||
|
|
||
| ## ArkType VS Code Extension | ||
| ArkEnv works great with modern code editors that support syntax highlighting for ArkType definitions. There are two levels of support you can choose from, depending on your needs and editor preferences. |
There was a problem hiding this comment.
I'm not a fan of the description and this paragraph. We're only talking about VS Code here anyway @copilot
There was a problem hiding this comment.
Simplified the description and removed the redundant introductory paragraph to focus specifically on VS Code as requested in commit fdd98ef.
| The [ArkType VS Code extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) provides syntax highlighting and inline error summaries for ArkType definitions, making your development experience with ArkEnv much more pleasant. | ||
| ## ArkType VS Code Extension: Syntax Highlighting and Error Lens | ||
|
|
||
| For VS Code users, the [ArkType extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) provides essential syntax highlighting and inline error summaries for your ArkEnv schemas. |
There was a problem hiding this comment.
| For VS Code users, the [ArkType extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) provides essential syntax highlighting and inline error summaries for your ArkEnv schemas. | |
| The [ArkType extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) provides syntax highlighting and inline error summaries for ArkEnv. |
There was a problem hiding this comment.
Applied the suggested change to make the ArkType extension introduction more direct and concise in commit fdd98ef.
There was a problem hiding this comment.
Applied the suggested change to simplify the ArkType extension description in commit dcec12c.
| - **Syntax highlighting** for ArkType definitions in your schema | ||
| - **Inline error summaries** via ErrorLens integration | ||
| - **Better developer experience** with visual feedback | ||
| - **Better developer experience** for common mistakes |
There was a problem hiding this comment.
| - **Better developer experience** for common mistakes | |
| - **Better DX** |
@copilot
There was a problem hiding this comment.
Changed to "Better DX" as suggested in commit dcec12c.
| ## ArkThemes: Special Highlighting | ||
|
|
||
| You can also use named imports, though you won't get syntax highlighting: | ||
| For an even better development experience, [ArkThemes](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes) provides special highlighting for TypeScript generics in ArkType definitions. This extension offers more comprehensive highlighting that makes ArkType schemas feel like native TypeScript code. |
There was a problem hiding this comment.
| For an even better development experience, [ArkThemes](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes) provides special highlighting for TypeScript generics in ArkType definitions. This extension offers more comprehensive highlighting that makes ArkType schemas feel like native TypeScript code. | |
| For an even better development experience, [ArkThemes](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkthemes) provides special highlighting for TypeScript generics in ArkType definitions. |
@copilot
There was a problem hiding this comment.
Updated the ArkThemes description to the suggested streamlined version in commit dcec12c.
…oduction Co-authored-by: yamcodes <2014360+yamcodes@users.noreply.github.com>
| ## Best Practices | ||
|
|
||
| - **Use default import** if you're using VS Code and want enhanced syntax highlighting | ||
| - **Use named import** if you prefer explicit imports or are using other editors | ||
| - **Use default import** (`import arkenv`) if you want syntax highlighting in VS Code or Cursor | ||
| - **Use named import** (`import { createEnv }`) if you prefer explicit imports or use other editors |
There was a problem hiding this comment.
| ## Best Practices | |
| - **Use default import** if you're using VS Code and want enhanced syntax highlighting | |
| - **Use named import** if you prefer explicit imports or are using other editors | |
| - **Use default import** (`import arkenv`) if you want syntax highlighting in VS Code or Cursor | |
| - **Use named import** (`import { createEnv }`) if you prefer explicit imports or use other editors | |
| ## Best Practices | |
| - **Use default import** (`import arkenv`) if you want syntax highlighting in VS Code, Cursor, or JetBrains IDEs | |
| - **Use named import** (`import { createEnv }`) if you prefer explicit imports or use other editors |
@copilot
There was a problem hiding this comment.
Updated the Best Practices section to include JetBrains IDEs and removed the consistency bullet point as suggested in commit dcec12c.
…se DX abbreviation, streamline ArkThemes description, and update Best Practices section Co-authored-by: yamcodes <2014360+yamcodes@users.noreply.github.com>
|
Closed in favor of #154 |
Restructured the "Integrating with VS Code" documentation to better explain the two levels of syntax highlighting support available for ArkEnv users.
Changes Made
Clearer positioning of syntax highlighting options:
Improved content organization:
Enhanced clarity:
Corrected ArkThemes information:
Final refinements:
Updated Best Practices section:
The restructured guide now clearly presents a progression from basic to enhanced syntax highlighting options, making it easier for users to choose the right setup for their development environment.
Fixes #152.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.