Skip to content

Fixes a bug in LocaleMatcher where locale parsing information is passed incorrectly#492

Merged
gouniLee merged 6 commits intodevelopmentfrom
localematcher
Apr 15, 2026
Merged

Fixes a bug in LocaleMatcher where locale parsing information is passed incorrectly#492
gouniLee merged 6 commits intodevelopmentfrom
localematcher

Conversation

@gouniLee
Copy link
Copy Markdown
Contributor

@gouniLee gouniLee commented Apr 8, 2026

Checklist

  • At least one test case is included for this feature or bug fix.
  • ReleaseNotes has added or is not needed.
  • This PR has passed all of the test cases on Nodejs and Chrome Browser.
  • This PR has passed all of the test cases on QT/QML.
  • This is an API breaking change.
  • Requires a major version change.

Issue Resolved / Feature Added

Align the variable names passed by Localematcher with the order expected by the actual Locale object to reduce confusion.
This change is not a bug and does not affect existing behavior.

// Locale.js
var Locale = function(language, region, variant, script) {
...

Resolution

Links

…ted by the actual Locale object to reduce confusion
@gouniLee gouniLee requested a review from ehoogerbeets April 8, 2026 06:41
@gouniLee gouniLee self-assigned this Apr 8, 2026
@gouniLee gouniLee changed the title Match Localematcher variable names to the Locale object’s parameter order to reduce confusion Fixes a bug in LocaleMatcher where locale parsing information is passed incorrectly Apr 9, 2026
Co-authored-by: Edwin Hoogerbeets <ehoogerbeets@gmail.com>
@gouniLee gouniLee merged commit e65e72c into development Apr 15, 2026
1 check passed
@gouniLee gouniLee deleted the localematcher branch April 15, 2026 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants