feat: add configurable voice transcription - #6860
Conversation
|
Rebased onto current The web path now uses NextChat’s same-origin proxy instead of requiring browser CORS from the transcription server; desktop builds continue to call local endpoints directly. Blank model values are rejected before upload, and the settings copy now follows the existing English/Simplified Chinese locale structure. Exact-head validation:
The only full-lint limitation remains the repository tooling crash in unchanged |
codeCraft-Ritik
left a comment
There was a problem hiding this comment.
Really solid work. I appreciate that the optimization focuses on eliminating unnecessary allocations while maintaining the same parser behavior. The additional regression tests around slicing, concatenation, and lazy evaluation make this a well-rounded change. 👏 @LauraGPT
46f6736 to
640c0b8
Compare
Signed-off-by: zhifu gao <18321252+LauraGPT@users.noreply.github.com>
640c0b8 to
4fd2ab7
Compare
Summary
/v1/audio/transcriptionsendpointThe defaults target a local FunASR/SenseVoice-compatible endpoint at
http://localhost:8000/v1, while remaining provider-agnostic. Web deployments use NextChat’s existing same-origin proxy boundary, so a colocated or network-reachable transcription service does not need browser CORS configuration.Validation
yarn test:ci --runInBand: 38 suites, 176 tests passedyarn tsc --noEmit: passedchat.tsx)yarn build: passedThe full
next lintcommand still hits the repository tooling crash in unchangedapp/constant.ts:1(unused-imports/no-unused-importsreadingloc); the production build completes despite reporting that same lint-plugin warning.Closes #6803