Once the type metadata gets merged #220 , we should consider I18N.
@OR13 Since you raised the point on #220 . would we need to consider I18N only for information that is displayed to end-users or also to information intended for developers, e.g., name/description?
Once the type metadata gets merged #220 , we should consider I18N.
@OR13 Since you raised the point on #220 . would we need to consider I18N only for information that is displayed to end-users or also to information intended for developers, e.g., name/description?