add full chatbot integration with worker proxy and markdown UI #830
+1,833
−59
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
for more information, see https://pre-commit.ci
…veloperFolio into implement-chat-branch
for more information, see https://pre-commit.ci
Author
|
To use the chatbot correctly,The user also need to change the CHAT_WORKER_URL, inside the chatConfig.js, for the one used to store the openAI API key + context for the chatbot. Readme.md changes may be needed to add this instruction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This pull request introduces the complete chatbot integration for the portfolio. It adds the Cloudflare Worker proxy responsible for handling OpenAI requests, configures CORS rules, and updates the frontend to consume the new /chat endpoint. The UI now supports Markdown rendering for model responses, improving readability for lists, emphasis and formatted content. These changes aim to make the assistant fully functional both locally and in production environments.
No new external dependencies affect the existing build, aside from enabling optional Markdown rendering on the client.
Fixes # (issue)
Type of change