Chat Localisation #829
-
Hey @demchenkoalex, in v1 we had the ability to customise the Chat widget and all the sub widgets by passing the ChatL10n class. I wonder if there is something one could do to migrate or have the same functionality or it is not something urgent now but is planned to be added back in later on in the library. Still migrating to v2 but enjoying all the various updates already. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey! There's nothing to localise anymore :) I changed the overall architecture so that package users define widgets through builders. This way, all text can be provided directly by the user - no need for a localisation class. For example:
So yes - with the new design, localisation class is no longer needed 🎉 |
Beta Was this translation helpful? Give feedback.
Hey! There's nothing to localise anymore :)
I changed the overall architecture so that package users define widgets through builders. This way, all text can be provided directly by the user - no need for a localisation class.
For example:
emptyChatListBuilder
and pass in any widget you like. You can still use my default EmptyChatList widget, which has atext
parameter you can localise yourself.composerBuilder
with the Composer widget I provide, you can pass in a localisedhintText
. Or you can create your own, custom Composer.So yes - with the new design, localisation class is no longer needed 🎉