shoelace-style/localize issues and pull requests

#21 - Use `@lit/context` to pass locale down from an arbitrary ancestor

Issue - State: closed - Opened by damooo 6 months ago

#20 - Language codes with underscores throw a `RangeError`

Issue - State: closed - Opened by claviska 9 months ago - 1 comment
Labels: bug

#19 - Type error with term method after updating typescript to version 5.1.3

Issue - State: open - Opened by samueldelaporte about 1 year ago - 1 comment

#18 - Prepare for SSR on [email protected]+

Pull Request - State: closed - Opened by whjvenyl about 1 year ago - 1 comment

#17 - Localize really needs something like `i18next.exists(...)`

Issue - State: closed - Opened by xdev1 over 1 year ago - 1 comment

#16 - Region detection algorithm not always working properly

Issue - State: closed - Opened by xdev1 over 1 year ago - 2 comments

#15 - fix: damn absolute paths...

Pull Request - State: closed - Opened by KonnorRogers almost 2 years ago

#14 - Approach of implicitly setting fallback language considered harmful

Issue - State: open - Opened by xdev1 about 2 years ago

#11 - Discussion: Alternative model to achieve type safe translations

Issue - State: closed - Opened by xdev1 about 2 years ago

#10 - Localize should update components when preferred language changes

Issue - State: closed - Opened by xdev1 about 2 years ago - 3 comments

#9 - Makes `LocalizeController` framework agnostic (see issue #8)

Pull Request - State: closed - Opened by xdev1 about 2 years ago - 1 comment

#8 - LocalizeController should also work with other webcomponent libraries, not only with Lit

Issue - State: closed - Opened by xdev1 about 2 years ago - 1 comment

#7 - Why does function `registerTranslation` not merge translations with same $code?

Issue - State: closed - Opened by xdev1 about 2 years ago - 5 comments

#6 - Original full lang value not available within translation functions

Issue - State: closed - Opened by xdev1 about 2 years ago - 7 comments

#5 - Getting rid of the depencency on Lit / etc.

Issue - State: closed - Opened by xdev1 over 2 years ago - 2 comments

#4 - Namespaces for translations

Issue - State: closed - Opened by mcjazzyfunky almost 3 years ago - 1 comment

#3 - Customizing base localization functionality

Issue - State: closed - Opened by mcjazzyfunky almost 3 years ago - 5 comments

#2 - On `forceUpdate` and `connectedElements`

Issue - State: closed - Opened by mcjazzyfunky almost 3 years ago - 6 comments

#1 - On `localize`s language detection strategy

Issue - State: closed - Opened by mcjazzyfunky almost 3 years ago - 3 comments

Ecosyste.ms: Issues

GitHub / shoelace-style/localize issues and pull requests