Skip to content

Bug: selectTranslateObject doesn't apply the fallback #519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
xliu011-becls opened this issue Oct 20, 2021 · 1 comment
Open
1 task done

Bug: selectTranslateObject doesn't apply the fallback #519

xliu011-becls opened this issue Oct 20, 2021 · 1 comment

Comments

@xliu011-becls
Copy link

xliu011-becls commented Oct 20, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Which Transloco package(s) are the source of the bug?

Transloco

Is this a regression?

No

Current behavior

GIVEN

  • Multiple translation files are present.
  • Config option missingHandler.useFallbackTranslation is enabled.

WHEN

  • Use selectTranslateObject to select translation which is only available in fallback translation file.

ACTUAL

  • No translation is returned, and a missing translation error is logged.

Expected behavior

  • The translation from fallback translation file is returned.

Please provide a link to a minimal reproduction of the bug

https://ngneat-transloco-ynvfpi.stackblitz.io/home

Transloco Config

No response

Please provide the environment you discovered this bug in

No response

Browser

No response

Additional context

The selectTranslate function and pipe work fine, they return result from the fallback translation file.

I would like to make a pull request for this bug

No

@ThummyTrubbel
Copy link

When can a fix be expected?

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

No branches or pull requests

2 participants