Skip to content
This repository was archived by the owner on Jun 23, 2025. It is now read-only.

fix(Core): Language config bug fixed#1775

Merged
3 commits merged into
sebholstein:masterfrom
alisahinozcelik:bugfix/language-config-does-not-work-at-forRoot
Dec 4, 2019
Merged

fix(Core): Language config bug fixed#1775
3 commits merged into
sebholstein:masterfrom
alisahinozcelik:bugfix/language-config-does-not-work-at-forRoot

Conversation

@alisahinozcelik

Copy link
Copy Markdown
Contributor

language config was not working when it is set in forRoot method

sahin added 2 commits November 29, 2019 19:54
language config was not working when it is set in forRoot method
@codecov

codecov Bot commented Nov 29, 2019

Copy link
Copy Markdown

Codecov Report

Merging #1775 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1775   +/-   ##
=======================================
  Coverage   47.97%   47.97%           
=======================================
  Files          47       47           
  Lines        1999     1999           
  Branches      177      177           
=======================================
  Hits          959      959           
  Misses       1036     1036           
  Partials        4        4
Impacted Files Coverage Δ
...e/services/maps-api-loader/lazy-maps-api-loader.ts 89.39% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c9e977...727b459. Read the comment docs.

@ghost

ghost commented Nov 30, 2019

Copy link
Copy Markdown

Thanks, I am embarassed as it's my bug.

Can you just add another test showing that when a LOCALE_ID and language are set, it will choose language

@alisahinozcelik

Copy link
Copy Markdown
Contributor Author

Thanks, I am embarassed as it's my bug.

Can you just add another test showing that when a LOCALE_ID and language are set, it will choose language

@doom777
Shouldn't it prefer choosing LOCALE_ID in that case. If you say ok, then I can implement that.

@ghost

ghost commented Dec 1, 2019

Copy link
Copy Markdown

No, because LOCALE_ID is always set to be the locale of the entire app. Language is an input you send specifically to Google Maps

@alisahinozcelik

Copy link
Copy Markdown
Contributor Author

No, because LOCALE_ID is always set to be the locale of the entire app. Language is an input you send specifically to Google Maps

Ok, I will add that spec.

@ghost ghost merged commit d2ef77c into sebholstein:master Dec 4, 2019
@erzaehlsalex

Copy link
Copy Markdown

@doom777 Can you please publish a new version with this fix? :)

@shreddison

Copy link
Copy Markdown

please publish :)

@aakici

aakici commented Mar 23, 2020

Copy link
Copy Markdown

@alisahinozcelik, @doom777 please note that the latest commit is not included in the latest npm package. (v1.1.0)

For that reason map language is set always with LOCALE_ID.

Could you please publish a fix. Thank you.

This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants