-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 t3-chat extension #16961
base: main
Are you sure you want to change the base?
Add t3-chat extension #16961
Conversation
- encode URI, remove console logs - update description - Update README.md - first commit
Congratulations on your new Raycast extension! 🚀 Due to our current reduced availability, 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. |
Yo! Excited about this one. Thanks for building. |
For sure! |
- Update README.md - Fix fallback command undefined - Update README.md
I went ahead and pushed a fix for a minor bug where the extension would not get the fallback text |
Hey @Lermatroid! Would you be open to merging our two extensions? I.e. adding some fetching functionality to this? You can see mine here: |
Hey @ParkerSm1th! I had considered doing something similar, but winded up not going that direction for a few reasons:
If theo / mark have any opinions on this I'd certainly be interested. In the meantime however, I went this route more closely resembling the Perplexity extension. If I am missing something here though certainly let me know and I'd be happy to discuss! |
extensions/t3-chat/lib/prefs.ts
Outdated
import { getPreferenceValues } from "@raycast/api"; | ||
|
||
interface Preferences { | ||
model: string; | ||
} | ||
|
||
export function getPrefs(): Preferences { | ||
return getPreferenceValues(); | ||
} |
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.
This is already built-in within raycast.d.ts
- you can remove this and reference Preferences
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.
Hey @pernielsentikaer, what type is this referring to? I don't see a type that is not a general Record<string, any>
that I can import and the docs outline doing it in the way that the PR does where you define a interface.
Edit: Ah nevermind I see, will push a update in a sec.
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.
Actually it would seem that I am unable to push the changes due this bug with the raycast publish command from another extension I have a PR up for
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.
We're looking into the bug with deleting files, are we good to go?
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.
Yep! Winded up pushing the edits via web ui. They worked locally so afaik they should work 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.
@pernielsentikaer I also quickly pushed a update that has the up-to-date model list in the package.json
Description
Quickly lets users create new chats on T3 Chat with the ability to choose which model to use.
Screencast
For some reason the github media upload did not want to work, so here is a YouTube link: https://youtu.be/40f4S--Hbfg
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder