Add english-conjugation extension#27298
Conversation
raycastbot
added
new extension
|
Congratulations on your new Raycast extension! 🚀 We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days. Once the PR is approved and merged, the extension will be available on our Store. |
Greptile SummaryThis PR adds a new Confidence Score: 5/5Safe to merge after addressing the changelog date placeholder; all other findings are minor style suggestions All findings are P2 — no correctness, data-integrity, or security issues were found. The extension is well-structured with proper Raycast conventions followed. CHANGELOG.md (missing date placeholder) and src/conjugate-verb.tsx (manual Arguments type) Important Files Changed
Prompt To Fix All With AIThis is a comment left during a code review.
Path: extensions/english-conjugation/CHANGELOG.md
Line: 3
Comment:
**Missing `{PR_MERGE_DATE}` placeholder**
The changelog entry is missing the required date placeholder and uses "Initial Version" instead of the conventional "Initial Release". Per Raycast convention, the date is auto-populated on merge — omitting it means the release will have no date in the store.
```suggestion
## [Initial Release] - {PR_MERGE_DATE}
```
**Rule Used:** What: In Raycast extension changelogs, `{PR_MERGE_... ([source](https://app.greptile.com/review/custom-context?memory=799af734-ebd9-4b40-9ffd-97a70fc71c8a))
How can I resolve this? If you propose a fix, please make it concise.
---
This is a comment left during a code review.
Path: extensions/english-conjugation/src/conjugate-verb.tsx
Line: 5-7
Comment:
**Manually defined `Arguments` type**
Command argument interfaces are auto-generated in `raycast-env.d.ts` when the extension runs. Manually defining `Arguments` here can go out of sync with the actual `package.json` argument declaration and creates a maintenance burden.
Remove this manual definition and rely on the generated type instead:
```suggestion
```
**Rule Used:** What: Don't manually define `Preferences` for `get... ([source](https://app.greptile.com/review/custom-context?memory=d93fc9fb-a45d-4479-a6a4-b1b4af98ebc8))
How can I resolve this? If you propose a fix, please make it concise.
---
This is a comment left during a code review.
Path: extensions/english-conjugation/src/conjugation.ts
Line: 34-36
Comment:
**No error handling around `conjugate()`**
The `eng-verber` library is called directly without a try/catch. If the library throws for unexpected inputs (e.g. numeric strings, punctuation, very long tokens), the entire command will crash with an unhandled error rather than showing an empty state. Wrapping this call in a try/catch and returning `[]` on failure would make the extension more resilient.
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "Prepare Raycast store submission" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| @@ -0,0 +1,7 @@ | |||
| # Changelog | |||
|
|
|||
| ## [Initial Version] | |||
There was a problem hiding this comment.
{PR_MERGE_DATE} placeholder
The changelog entry is missing the required date placeholder and uses "Initial Version" instead of the conventional "Initial Release". Per Raycast convention, the date is auto-populated on merge — omitting it means the release will have no date in the store.
| ## [Initial Version] | |
| ## [Initial Release] - {PR_MERGE_DATE} |
Rule Used: What: In Raycast extension changelogs, `{PR_MERGE_... (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: extensions/english-conjugation/CHANGELOG.md
Line: 3
Comment:
**Missing `{PR_MERGE_DATE}` placeholder**
The changelog entry is missing the required date placeholder and uses "Initial Version" instead of the conventional "Initial Release". Per Raycast convention, the date is auto-populated on merge — omitting it means the release will have no date in the store.
```suggestion
## [Initial Release] - {PR_MERGE_DATE}
```
**Rule Used:** What: In Raycast extension changelogs, `{PR_MERGE_... ([source](https://app.greptile.com/review/custom-context?memory=799af734-ebd9-4b40-9ffd-97a70fc71c8a))
How can I resolve this? If you propose a fix, please make it concise.| type Arguments = { | ||
| verb?: string; | ||
| }; |
There was a problem hiding this comment.
Arguments type
Command argument interfaces are auto-generated in raycast-env.d.ts when the extension runs. Manually defining Arguments here can go out of sync with the actual package.json argument declaration and creates a maintenance burden.
Remove this manual definition and rely on the generated type instead:
| type Arguments = { | |
| verb?: string; | |
| }; |
Rule Used: What: Don't manually define Preferences for `get... (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: extensions/english-conjugation/src/conjugate-verb.tsx
Line: 5-7
Comment:
**Manually defined `Arguments` type**
Command argument interfaces are auto-generated in `raycast-env.d.ts` when the extension runs. Manually defining `Arguments` here can go out of sync with the actual `package.json` argument declaration and creates a maintenance burden.
Remove this manual definition and rely on the generated type instead:
```suggestion
```
**Rule Used:** What: Don't manually define `Preferences` for `get... ([source](https://app.greptile.com/review/custom-context?memory=d93fc9fb-a45d-4479-a6a4-b1b4af98ebc8))
How can I resolve this? If you propose a fix, please make it concise.| if (!infinitive) { | ||
| return []; | ||
| } |
There was a problem hiding this comment.
conjugate()
The eng-verber library is called directly without a try/catch. If the library throws for unexpected inputs (e.g. numeric strings, punctuation, very long tokens), the entire command will crash with an unhandled error rather than showing an empty state. Wrapping this call in a try/catch and returning [] on failure would make the extension more resilient.
Prompt To Fix With AI
This is a comment left during a code review.
Path: extensions/english-conjugation/src/conjugation.ts
Line: 34-36
Comment:
**No error handling around `conjugate()`**
The `eng-verber` library is called directly without a try/catch. If the library throws for unexpected inputs (e.g. numeric strings, punctuation, very long tokens), the entire command will crash with an unhandled error rather than showing an empty state. Wrapping this call in a try/catch and returning `[]` on failure would make the extension more resilient.
How can I resolve this? If you propose a fix, please make it concise.
|
This pull request has been automatically marked as stale because it did not have any recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊 |
2 participants
Description
Adds a new Raycast extension,
english-conjugation, that helps users quickly look up essential English verb forms in a minimal interface.What it does:
Store-prep work included in this submission:
npm run lintandnpm run buildScreencast
A screenshot is included in the
metadatafolder for this straightforward single-command extension.Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare placed outside of themetadatafolder