-
-
Notifications
You must be signed in to change notification settings - Fork 2
feat: asturian + shared RomanceNumberExtractor class #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
JarbasAl
wants to merge
13
commits into
dev
Choose a base branch
from
ast
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e89e084
feat: asturian
JarbasAl 65c15fa
refactor: utils.py typing
JarbasAl ec9e39d
feat: shared RomanceNumberExtractor class
JarbasAl 1a5406e
refactor: update imports
JarbasAl 11a6e54
add deprecation warnings
JarbasAl 7ceef03
fix: negative handling
JarbasAl 2714095
fix: imports
JarbasAl 971d773
Apply suggestions from code review
JarbasAl 69f2f64
fix: asturian missing number words
JarbasAl 4cd17ac
feat: expand pt number range for short/long scale
JarbasAl 7c27d20
fix: respect default number scale per lang
JarbasAl abb45b3
fix: add mwl tests
JarbasAl c82b4ec
port gl to new shared class
JarbasAl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: OpenVoiceOS/ovos-number-parser
Length of output: 222
🏁 Script executed:
Repository: OpenVoiceOS/ovos-number-parser
Length of output: 11500
Fix Portuguese variant handling in
numbers_to_digits,is_fractional, andis_ordinal.The dispatch logic is inconsistent across functions.
pronounce_number,pronounce_fraction,pronounce_ordinal, andextract_numberall check"br" in lang.lower()to route Brazilian Portuguese separately, butnumbers_to_digits(line 72),is_fractional(line 341), andis_ordinal(line 368) always route toPT_PTregardless of whether the language ispt-BRor similar. This means Brazilian Portuguese users receive Portugal-specific behavior for these three functions.🤖 Prompt for AI Agents