-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
[core] Added i18n feature for profiles #785
Conversation
Signed-off-by: Christoph Weitkamp <[email protected]>
00c0925
to
270b6f5
Compare
Signed-off-by: Christoph Weitkamp <[email protected]>
d0af285
to
f144438
Compare
Signed-off-by: Christoph Weitkamp <[email protected]>
f144438
to
d99224d
Compare
What about a
Okay, while reading the classes, I assume we don't need generics at all.
The type of the key does not matter. |
Yes, sounds good. Moving it to an own class in the i18n package. Another question which came to my mind was if it is the right place to use the localized caches in the Independently of the final approach we should do it in a separate PR to keep the history clean. |
👍 IMHO also the |
Of course. I already have it in the pipe. |
Signed-off-by: Christoph Weitkamp <[email protected]> GitOrigin-RevId: b5f33d3
One comment: There is an internal class
LocalizedProfileTypeKey
which is used in a very similar way for other translatable objects (e.g. https://github.com/openhab/openhab-core/blob/master/bundles/org.openhab.core.thing/src/main/java/org/eclipse/smarthome/core/thing/DefaultSystemChannelTypeProvider.java#L281-L328 and https://github.com/openhab/openhab-core/blob/master/bundles/org.openhab.core.config.xml/src/main/java/org/eclipse/smarthome/config/xml/AbstractXmlBasedProvider.java#L40-L79). I am not very happy with that and think about a refactoring. Let me know your opinion.Signed-off-by: Christoph Weitkamp [email protected]