Skip to content

feat(http-loader): handle multiple ressources & silent #1566

@rbalet

Description

@rbalet

Current behavior

Actually, we can only target one ressource folder

Expected behavior

Being able to select multiple one

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

Remove the use of the external : https://www.npmjs.com/package/ngx-translate-multi-http-loader library for no additional cost

How do you think that we should implement this?

The http-loader could accept, instead of prefix and suffix, a new resource and/or resources object.

export interface TranslationResource {
  prefix: string
  suffix?: string
  optional?: boolean
}

Optional

We could add an optional variable, which silent the HTTP call if there is an error
(It's also a long time wished issue)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions