Conversation
a-augustin
requested review from
a team,
Fryingpannn and
nang-dev
as code owners
|
Ohhh sorry augustin. we should have it be automatic! so theyre already signed in. client side (the app) can just send their api key and the feedback as text. so just one box -> feedback and one button -> send. and we should have auto close, with a vscode notif in the bottom right that says "Feedback sent successfully!" (or error) so basically:
my bad for not making this clear earlier |
|
No worries! I’ll make the changes. Thanks for the feedback |
|
I updated the feedback page with just the text box and the vscode notifications when the user submits. I also added the headers and API key to the endpoint you mentioned. If there are any issues, let me know. |
| const router = createMemoryRouter([ | ||
| { | ||
| initialEntries: [window.isPearOverlay ? "/inventory" : window.initialRoute], | ||
| path: "/", |
There was a problem hiding this comment.
why is all this removed?
| { | ||
| path: "/feedback", | ||
| element: <Feedback/>, | ||
| }, |
There was a problem hiding this comment.
you can just add /feedback route here, leave the rest as it is 😄
| "/apiKeyOnboarding", | ||
| "/aiderMode", | ||
| "/inventory", | ||
| "/inventory/aiderMode", | ||
| "/inventory/perplexityMode" | ||
| ]; |
There was a problem hiding this comment.
dont remove these, we want to hide footers on those routes
There was a problem hiding this comment.
I didn't remove those footer line, I'm not sure how they were removed.
This reverts commit e7ae292.
|
Whatever happened with this? Are you guys still looking to have a feedback option? |
4 participants
Description ✏️
I added the feedback page in the submodule.
Checklist ✅