refactor(MessageHandler -> useServerStream): TS Conversion and Custom Hook instead of RFC #818
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.
Summary
refactor(MessageHandler -> useServerStream): convert all relating files to TS and correct typings based on this change: properly refactor MessageHandler to a custom hook (it was being used as a React Functional Component or RFC before), where it's passed a submission object to instantiate the stream. This is the bare minimum groundwork for potentially having multiple streams running, which would be a big project to modularize a lot of the global state into maps/multiple streams, particular useful for having multiple views or AI conversation in view.
Also fixed an issue with the abortMiddleware, to allow it to behave as expected even when aborted too "early" for the server (before the convoId is generated), In this case, the userId will be used as the abortKey. This should help with more reliability to the stop/continue e2e test.
Change Type
Testing
Manual tests confirm no breaking changes, PR will determine how automated tests do.
Checklist