sorb/ThreadNet-Web
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 4 Wiki Activity

Use oxlint to apply jsx/tsx extension consistently (#34303)

Browse Source 
* Remove stale max-len disablements

* Remove stale camelCase & naming-convention disablements

* Remove stale ban-ts-comment disablements

* Remove stale no-var disablements

* Remove stale no-empty-property disablements

* Remove stale react rule disablements

* Remove stale no-constant-condition disablements

* Remove stale no-unused-vars disablements

* Remove stale disablements for disabled rules

* fixup camelcase

* Remove dead code

* Tidy code

* Tweak oxlint config

* Use oxlint to apply jsx/tsx extension consistently

* Fix import

* Fix imports

* Rename affected snapshots

* Update more imports
This commit is contained in:
Michael Telatynski
2026-07-17 09:50:57 +00:00
committed by GitHub
parent 63b8974051
commit 79ac7fbc9e
144 changed files with 24 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/translating-dev.md
+1 -1
View File
@@ -8,7 +8,7 @@
## Translating strings vs. marking strings for translation
Translating strings are done with the `_t()` function found in `languageHandler.tsx`.
Translating strings are done with the `_t()` function found in `languageHandler`.
It is recommended to call this function wherever you introduce a string constant which should be translated.
However, translating can not be performed until after the translation system has been initialized.
Thus, sometimes translation must be performed at a different location in the source code than where the string is introduced.