chore(demo-web): update page range parser model#108
Merged
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
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.
Affected Package(s)
@heripo/pdf-parser@heripo/document-processor@heripo/model@heripo/logger@heripo/shared(internal)demo-webdocsSummary
This PR updates the default page range parser model used by the demo web upload flow. The change moves the page range parsing default from the previous Gemma model to the Qwen 3.6 35B MLX model so new processing requests use the updated local model configuration.
Changes
DEFAULT_FORM_VALUES.pageRangeParserModelinapps/demo-web/src/features/upload/types/form-values.ts.lmstudio/gemma-4-31b-it-mlxwithlmstudio/qwen3.6-35b-a3b-mlxfor page range parsing defaults.Breaking Changes
Checklist
pnpm lintpnpm typecheckpnpm buildpnpm testRelated Issues
Closes #