feat: add ${custom_words} placeholder to post-processing prompts - #1711
Open
djurcola wants to merge 2 commits into
Open
feat: add ${custom_words} placeholder to post-processing prompts#1711djurcola wants to merge 2 commits into
djurcola wants to merge 2 commits into
Conversation
Owner
|
This is probably a good change, I will try and merge it when I get a chance |
Author
|
I am running it locally and it makes post processing almost perfect, would be great to get it into the main branch! |
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
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.
Summary
${custom_words}placeholder support to post-processing prompt templates(none provided)fallback when the custom-word list is empty${output}and${custom_words}in the English prompt UIMotivation
Custom words already help transcription correction, but post-processing prompts cannot currently reference the configured list. This lets users include the same domain-specific vocabulary in their LLM instructions without duplicating it manually.
Testing
cargo fmt --check --manifest-path src-tauri/Cargo.toml— passednpm run lint— passednpm run build— passedsrc/i18n/locales/en/translation.json— passedgit diff --check— passedThe full Cargo test target could not compile on the local Linux host because
pkg-config/GLib development tooling is unavailable; it failed while buildingglib-sys, before compiling Handy. The focused renderer was therefore compiled and exercised independently withrustc --test.Compatibility
${output}behavior is preservedAI assistance disclosure
Yes. OpenCode using the Codex-backed GPT-5.6 Sol model assisted with adapting the existing fork implementation to current upstream, and Hermes Coder reviewed the diff and ran verification. The final changes were constrained to the two feature-relevant files.