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
feature(transloco): Use MessageFormatTranspiler with FunctionalTranspiler #705
Comments
@MikeDabrowski I'll have to consider how since it wasn't raised before. |
We have an alert type component - just a rectangle with background and text we display to notify user of some important things. That already has translation that uses markdown. Now UX has the idea that we need to show additionally a list of errors there. If But those errors each has to be translated as well. I thought maybe I could just append the translated errors for markdown to render them. But I thought the logic to do so would be best moved to such function. I tried to merge Functional and MessageFormat ones but the fn didn't work. In the end (we need this done by the end of this week) I just created new component and have two regular translations. |
We just got another feature where this fn would be useful - need to replace some parts of translations based on dynamic config. |
Is there an existing issue for this?
Which Transloco package(s) will this feature affect?
MessageFormat
Is your feature request related to a problem? Please describe
Is there a way to combine the MessageFormatTranspiler and FunctionalTranspiler?
Current impl of MessageFormatTranspiler extends DefaultTranspiler. I havent found any hint in the docs apart creating custom one myself.
Describe the solution you'd like
No response
Describe alternatives you've considered
Additional context
No response
I would like to make a pull request for this feature
Yes 🚀
The text was updated successfully, but these errors were encountered: