Update OneLook Thesaurus extension

[FelipeCortez]

Description

Fixes API access by switching the provider from www.onelook.com to api.datamuse.com. Also formats parts of speech in the definitions view.

Screencast

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 the update! 🎉

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

[greptile-apps]

Greptile Summary

This PR fixes API access by switching the endpoint from www.onelook.com to api.datamuse.com, and adds a formatPOS helper to render parts of speech as inline code in the detail view. The changelog entry uses a hardcoded date (2026-04-06) instead of the required {PR_MERGE_DATE} placeholder, which needs to be corrected before merging.

Confidence Score: 4/5

Safe to merge after fixing the changelog date placeholder

The code change is clean and correct; the one blocker is the hardcoded date in CHANGELOG.md that must use {PR_MERGE_DATE} per project convention

CHANGELOG.md requires the date placeholder fix

Important Files Changed

Filename	Overview
extensions/onelook-thesaurus/CHANGELOG.md	New changelog entry uses a hardcoded date instead of the required {PR_MERGE_DATE} placeholder
extensions/onelook-thesaurus/src/search.tsx	Switches API endpoint to api.datamuse.com and adds POS formatting in detail view; list subtitle still shows raw POS string

Comments Outside Diff (1)

1. extensions/onelook-thesaurus/src/search.tsx, line 44 (link)

   Raw POS tag visible in list subtitle

   The new formatPOS helper is applied in the detail markdown but not here, so the list subtitle still shows the raw tab-separated POS prefix (e.g. n definition text). Consider applying the same formatting for consistency.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: extensions/onelook-thesaurus/src/search.tsx
   Line: 44
   
   Comment:
   **Raw POS tag visible in list subtitle**
   
   The new `formatPOS` helper is applied in the detail markdown but not here, so the list subtitle still shows the raw tab-separated POS prefix (e.g. `n	definition text`). Consider applying the same formatting for consistency.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

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

Comment:
**Hardcoded date instead of `{PR_MERGE_DATE}` placeholder**

Changelog entry titles must use the `{PR_MERGE_DATE}` placeholder so the merge date is automatically populated during release — using a hardcoded date will not be replaced and breaks the standard convention.

```suggestion
## [Enhancements] - {PR_MERGE_DATE}
```

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

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/onelook-thesaurus/src/search.tsx
Line: 44

Comment:
**Raw POS tag visible in list subtitle**

The new `formatPOS` helper is applied in the detail markdown but not here, so the list subtitle still shows the raw tab-separated POS prefix (e.g. `n	definition text`). Consider applying the same formatting for consistency.

```suggestion
          subtitle={word.defs?.[0] ? formatPOS(word.defs[0]) : undefined}
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Update changelog" | Re-trigger Greptile}