Closed kazu0617 closed 3 years ago
I think it is a good idea to not include the space before the colon, I can definitely accept this!
Currently there is a conflict with en.json. Are you able to update it so it doesn't cause a merge conflict on your end?
Currently there is a conflict with en.json. Are you able to update it so it doesn't cause a merge conflict on your end?
Thank you. I have resolved the conflicts so now be able to merge.
Thank you very much! Merged!
It is better to decide on the notation before merging, but it is customary for Json to not include a space before the colon (in fact, in some cases, this is automatically reflected when saving using VSCode). In addition, the MMC text added this time is also written in this way.
So, if it is possible, I would like to see this notation unified. If you want to unify the notation with the one with spaces, I will rewrite the PR to that one. Thank you very much for your cooperation.