video1.0<iframe src="https://www.loom.com/embed/a2b7f9e6d8954beca8dcb0a0a778b27a" frameborder="0" width="3442" height="2581" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>25813442Loomhttps://www.loom.com25813442https://cdn.loom.com/sessions/thumbnails/a2b7f9e6d8954beca8dcb0a0a778b27a-00001.gif134.440711611In this video, I discuss the possibility of implementing type safety in the inline message format plugin for storing translations as a message.json file. Currently, translations are stored as an array in the JSON, but I propose nesting the array within an object to enable the use of the dollar schema for linting. This change would provide type safety and prevent manual changes to the translations that could break the plugin. I also explore the potential for future extendability with a data schema. I would like your input on whether or not to implement this type safety.