Add useChat() hook and ChatProvider context #822
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.
Fixes #818, adding a new
<ChatProvider />
context and associateduseChat()
hook. We can use this to access the currentchat
anywhere in the React tree without props.After this lands, it would be nice to refactor our code to not bother passing the chat via props all the time.
You can test this by trying to have the LLM write SQL that references one of the files or tables in DuckDB (e.g.,
select * from chatcraft.chats
) and then clicking the run button to execute it.