refactor: remove Qwik GPT AI from the docs search #6314
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ Deploy Preview for qwik-insights failed.
|
|
is this the same? |
Yep, it's a dupicate. Closing this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
What is it?
Description
We had a meeting regarding docs, and our consensus was that the Qwik GPT feature is not helpful in providing a good search experience to those looking to figure out how or why they should build with Qwik.
This PR tries to remove any lingering Qwik GPT code. While I'm sure some of us might get the feeling that we should comment it out and save it for later, I believe the reality is that would remain code in the codebase. We can always look in the file history and get it back if we really need it.
TODO: please review the
packages/docs/src/routes/query/[id]/index.tsxfile.Happy to continue this PR once those questions are answered 👍 . Would greatly appreciate the time taken to review this.
Use cases and why
Checklist: