-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add early-tools-news extension #16169
Conversation
Congratulations on your new Raycast extension! 🚀 You can expect an initial review within five business days. Once the PR is approved and merged, the extension will be available on our Store. |
Hi 👋 Thanks for your contribution 🔥 Could you look into the CI errors mentioned here so I can review it |
- Final prettification. - Fixed CLI error.
Hi.
These should be resolved now. :) Excited to see this go live – I can edit details, screenshots and make changes to the code (if needed for more sources) once published, correct?
Thanks!
… On 12.01.2025, at 08:46, Per Nielsen Tikær ***@***.***> wrote:
Hi 👋
Thanks for your contribution 🔥
Could you look into the CI errors mentioned here <https://github.com/raycast/extensions/actions/runs/12698693818/job/35397717884?pr=16169> so I can review it
—
Reply to this email directly, view it on GitHub <#16169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN4JCG4WYOXOM6CRXK4LQTD2KIMVNAVCNFSM6AAAAABUTOW7PGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVGYZDMMZQGI>.
You are receiving this because you authored the thread.
|
const [state, setState] = useState<State>({ items: [], isLoading: true }); | ||
const [searchText, setSearchText] = useState(""); | ||
|
||
useEffect(() => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can maybe use useCachedPromise from @raycast/utils
here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea! Does this stop the plugin from being released on the store? Happy to make the changes, just need to know :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can indeed make the change, when you publish it just updates the PR
Description
Screencast
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder