Internationalization is a big problem. If you want your application to make a worldwide impact, you have to deal with language barriers. Before your application can succeed outside the English-speaking world, you’ll have to adapt all your strings, dates, and numbers to the conventions of different cultures. Developers call this practice internationalization (which is often abbreviated to “i18n,” because there are 18 letters between the ‘I’ and the ’n’ in the word Internationalization. One of the most important part comes after the development of your application is the languages in which it should get translated according to the users requirement. With the change in the languages will certainly change the format of viewing for the fields like numbers format, currencies ,units etc., The solution to handle all the above barriers is the "i18n". But internationalization doesn’t have to be hard, thanks to a new React library. React-Intl is an open-source project from Yahoo...
In this Blog will cover more advanced JSX . You'll learn some powerful tricks, and some common errors to avoid.If you haven't gone through the basic JSX which we have covered i will recommend to go through the JSX blog first and come back to this . Grammar in JSX is mostly the same as in HTML, but there are subtle differences to watch out for. Probably the most frequent of these involves the word class . In HTML, it's common to use class as an attribute name: <h1 class="big">Hey</h1> In JSX , you can't use the word class ! You have to use className instead: <h1 className="big">Hey</h1> This is because JSX gets translated into JavaScript, and class is a reserved word in JavaScript. When JSX is rendered , JSX className attributes are automatically rendered as class attributes. Another JSX 'gotcha' involves self-closing tags . What's a self-closing tag? Most HTML elements use two tags: an openin...