Update easydict extension

[maxchang3]

Description

⚠️ Behavioral Changes

🆕 Custom AI Providers

• Connect LLMs through Raycast AI or any OpenAI-compatible endpoint for translation and word lookup.
• Existing settings migrate automatically. Open Search Word or Manage Providers to convert configured OpenAI and Gemini settings into ordinary AI providers, preserving connection settings, enablement, and ordering. Previously imported providers keep their edits; previously retired providers stay removed.
• Manage AI providers in Manage Providers. Old Extension Settings remain available as import sources, but no longer run separate providers. Editing, disabling, or deleting an AI provider does not restore an old service. Use Add from Legacy OpenAI/Gemini Settings… to create another copy, initially disabled.
• Provider ordering is now managed in Manage Providers. Built-in and AI providers share one order and can be moved together with the Move Up/Move Down actions or Cmd+Shift+Up/Down on macOS and Ctrl+Shift+Up/Down on Windows. The Legacy Service List Order preference only initializes this order until it is saved.

✨ New Features

AI-Generated Dictionary Entries

• For each provider, choose Plain Translation or AI-Generated Dictionary Entry in Word & Term Results.
• Dictionary mode applies to words and terms; other input remains plain translation. New or connection-related provider changes offer Test & Save by default, with Save Without Testing still available. JSON output defaults follow provider presets. Explicitly unsupported native JSON switches the provider to prompt-based output and shows a notice; malformed output is retried once without changing the setting. Dictionary generation may take longer.

Chinese Stroke Order

• Use Show Stroke Order from live or saved translation results to view stroke-order diagrams for Chinese characters.
  • Thanks to @MagEk1511

Screencast

Custom AI Providers	Chinese Stroke Order

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

[raycastbot]

Thank you for your contribution! 🎉

🔔 @tisfeng @ViGeng @LitoMore you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="ext/easydict"
FORK_URL="https://github.com/maxchang3/raycast-extensions.git"
EXTENSION_NAME="easydict"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Greptile Summary

This PR substantially updates Easydict with configurable AI providers, AI-generated dictionary entries, unified provider ordering and migration, and Chinese stroke-order views.

• Adds custom OpenAI-compatible and Raycast AI provider configuration, discovery, testing, persistence, and runtime integrations.
• Adds structured AI dictionary generation with parsing, retries, and fallback behavior.
• Adds provider management, ordering, legacy-setting migration, and expanded automated coverage.
• Adds stroke-order rendering and access from live and saved translation results.
• Updates extension metadata, documentation, assets, dependencies, and changelog.

Confidence Score: 4/5

The implementation appears functionally safe, but the explicit changelog placeholder requirement must be restored before merging.

Both previous concurrency findings were manually resolved and are not outstanding. The only remaining issue is the hard-coded changelog date, which violates the repository’s merge-date placeholder requirement.

Files Needing Attention: extensions/easydict/CHANGELOG.md

Important Files Changed

Filename	Overview
extensions/easydict/CHANGELOG.md	Documents the release features, but the latest revision hard-codes the merge date instead of retaining the required placeholder.
extensions/easydict/src/ai-providers/repository.ts	Implements serialized AI-provider persistence and migration state management; the previously reported concurrent-update finding is resolved.
extensions/easydict/src/components/pages/ProviderManagementPage.tsx	Implements unified provider management and serialized reorder actions; the previously reported rapid-reorder finding is resolved.
extensions/easydict/src/hooks/useQueryEngine.ts	Integrates AI-provider profiles, migration, provider ordering, and dictionary-mode query execution.
extensions/easydict/src/components/pages/StrokeOrderPage.tsx	Adds the Chinese stroke-order diagram view and its navigation behavior.

Prompt To Fix All With AI

### Issue 1
extensions/easydict/CHANGELOG.md:3
**Hard-Coded Changelog Date**

This heading replaces the required `{PR_MERGE_DATE}` template with `2026-09-09`. The repository requires changelog headings to retain that placeholder so merge automation can populate the date, and this requirement must be satisfied before merging.

```suggestion
## [v3.2.0] - {PR_MERGE_DATE}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (8): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​xsai/​shared-chat@​0.5.0-beta.6 ⏵ 0.5.0	+10
	npm/​@​xsai/​stream-text@​0.5.0-beta.6 ⏵ 0.5.0	+8		+1
	npm/​@​commitlint/​cli@​21.0.1 ⏵ 21.2.2			+1
	npm/​node-html-parser@​9.0.1
	npm/​@​commitlint/​config-conventional@​21.0.1 ⏵ 21.2.2

View full report

[pernielsentikaer]

Hi @maxchang3 👋

Thanks for the provider-management improvements 💪

The configuration-reset action in extensions/easydict/src/components/pages/ProviderManagementPage.tsx currently calls controller.update, which rejects invalid or unsupported saved data before the reset callback runs. This prevents recovery from the error screen.

Could you use saveAIProviderState for the confirmed reset, then reload the controller? For example, with the corresponding imports:

try {
  await saveAIProviderState({
    ...createEmptyAIProviderState(),
    migratedLegacyProviders: [...LEGACY_AI_PROVIDER_NAMES],
  });
  await controller.revalidate();
} catch (error) {
  await showFailureToast(error, {
    title: "Failed to Reset AI Provider Configuration",
  });
}

Please add regression coverage for malformed JSON, invalid configuration shapes, and unsupported versions.

---

I’ll convert this PR into a draft after submitting this review. Please press Ready for review when it’s ready and we’ll have a look 😊

[maxchang3]

@pernielsentikaer

Thanks for catching this! Fixed in b61f48a.

Reset now uses a dedicated resetAIProviderConfiguration path and revalidates the controller afterward, with failures surfaced via showFailureToast.

I also added regression tests for malformed JSON, invalid v1/v2 configuration shapes, and unsupported versions, verifying that invalid data is preserved until reset is confirmed and only then replaced with an empty configuration.

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/isfeng/easydict

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.

[greptile-apps]

Hard-Coded Changelog Date

This heading replaces the required {PR_MERGE_DATE} template with 2026-09-09. The repository requires changelog headings to retain that placeholder so merge automation can populate the date, and this requirement must be satisfied before merging.

Suggested change

	## [v3.2.0] - 2026-09-09
	## [v3.2.0] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE}... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/easydict/CHANGELOG.md
Line: 3

Comment:
**Hard-Coded Changelog Date**

This heading replaces the required `{PR_MERGE_DATE}` template with `2026-09-09`. The repository requires changelog headings to retain that placeholder so merge automation can populate the date, and this requirement must be satisfied before merging.

```suggestion
## [v3.2.0] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}`... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.