Every user displayed message/text should be a string resource object

[ReCodee]

trafficstars

Summary:

We should make a string resource object for every user displayed message/text, so that if in the future we plan to add multi-language functionality, then we can easily provide a multi-language alternative.

For eg:- we have many variables declared inside Constants.java which contain user displayed message/text and could be a hindrance in the future while adding multi-language functionality.

[ReCodee]

@devansh-299 @shiv07tiwari Can I work on this issue?

[shiv07tiwari]

@ReCodee This is a good issue. In this, I would like to give a suggestion:- As you said that we should shift to XML files because of the multi-language support. So it's better to add those strings in it that are displayed to the user. All other strings that are being used internally can be kept in Constatnts.java

[ReCodee]

@ReCodee This is a good issue. In this, I would like to give a suggestion:- As you said that we should shift to XML files because of the multi-language support. So it's better to add those strings in it that are displayed to the user. All other strings that are being used internally can be kept in Constatnts.java

Thanks for the suggestion :), I'll make changes accordingly.

[therajanmaurya]

Fixed in compose implementation