Skip to content

Export TranslateStore  #857

Closed
Closed
@hspier

Description

@hspier

Current behavior

TranslateStore is exported as a private Angular symbol (ɵa) but there are situations where it is needed to be accessed when implementing a TranslateLoader for example.

Expected behavior

TranslateStore is exported publicly.

What is the motivation / use case for changing the behavior?

There are certain use cases where the store needs to be accessible. One such example is an application that has a common bundle that is loaded at startup and has another bundle specific per area of the app. The specific bundle is lazily loaded. When changing locale, both bundles needs to be refreshed and this can be accomplished when accessing the store (since the translate service might or might not be the root service).

How do you think that we should implement this?

This is a rather straightforward ask and should be easy to implement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions