* remove unnecessary if `Array.prototype.some` already returns a boolean so an if to return true or false is completely unnecessary in this case. * perf: use count instead of find When using `count` instead of `findOneBy`, the data is not unnecessarily loaded. * remove duplicate null check The variable is checked for null in the lines above and the function returns if so. Therefore, it can not be null at this point. * simplify `getJsonSchema` Because the assigned value is `null` and the used keys are only shallow, use of `nestedProperty.set` seems inappropriate. Because the value is not read, the initial for loop can be replaced by a `for..in` loop. Since all keys will be assigned `null`, the condition of the ternary expression in the nested function will always be true. Therefore the recursion case will never happen. With this the nested function can be eliminated. * remove duplicate condition The code above already checks `dragging` and returns if it is truthy. Checking it again later is therefore unnecessary. To make this more obvious the `return` is removed in favour of using an if...else construct. * remove impossible "unknown" time The `ago` variable will always be a number and all non-negative numbers are already covered by other cases, the negative case is handled with `future` so there is no case when `unkown` could be achieved. |
||
|---|---|---|
| .. | ||
| README.md | ||
| ar-SA.yml | ||
| bn-BD.yml | ||
| ca-ES.yml | ||
| cs-CZ.yml | ||
| da-DK.yml | ||
| de-DE.yml | ||
| en-US.yml | ||
| es-ES.yml | ||
| fr-FR.yml | ||
| hr-HR.yml | ||
| ht-HT.yml | ||
| id-ID.yml | ||
| index.d.ts | ||
| index.js | ||
| it-IT.yml | ||
| ja-JP.yml | ||
| ja-KS.yml | ||
| jbo-EN.yml | ||
| kab-KAB.yml | ||
| kn-IN.yml | ||
| ko-KR.yml | ||
| nl-NL.yml | ||
| no-NO.yml | ||
| pl-PL.yml | ||
| pt-PT.yml | ||
| ro-RO.yml | ||
| ru-RU.yml | ||
| si-LK.yml | ||
| sk-SK.yml | ||
| th-TH.yml | ||
| tr-TR.yml | ||
| ug-CN.yml | ||
| uk-UA.yml | ||
| vi-VN.yml | ||
| zh-CN.yml | ||
| zh-TW.yml | ||
README.md
DO NOT edit locale files except ja-JP.yml.
When you add text to the ja-JP file (of misskey-dev/misskey), it will automatically be applied to other language files. Translations added in ja-JP file should contain the original Japanese strings.
Please see Contribution guide for more information.