Mirrored_Repos/InvokeAI
1
0
Fork 0
mirror of https://github.com/invoke-ai/InvokeAI synced 2024-08-30 20:32:17 +00:00
Code Issues Packages Projects Releases Wiki Activity
bc12ca9220
InvokeAI/invokeai/frontend/web/src/i18.d.ts

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

21 lines
487 B
TypeScript
Raw Normal View History

fix(ui): improve IDE TS performance by not resolving JSON The TS Language Server slows down immensely with our translation JSON, which is used to provide kinda-type-safe translation keys. I say "kinda", because you don't get autocomplete - you only get red squigglies when the key is incorrect. To improve the performance, we can opt out of this process entirely, at the cost of no red squigglies for translation keys. Hopefully we can resolve this in the future. It's not clear why this became an issue only recently (like past couple weeks). We've tried rolling back the app dependencies, VSCode extensions, VSCode itself, and the TS version to before the time when the issue started, but nothing seems to improve the performance. 1. Disable `resolveJsonModule` in `tsconfig.json` 2. Ignore TS in `i18n.ts` when importing the JSON 3. Comment out the custom types in `i18.d.ts` entirely It's possible that only `3` is needed to fix the issue. I've tested building the app and running the build - it works fine, and translation works fine.
2023-06-29 01:24:20 +00:00
// TODO: Disabled for IDE performance issues with our translation JSON
[WebUI] Localization Support (#2050) * Initial Localization Implementation * Fix Initial Spinner * Language Picker Dropdown * RU Localization Update Co-Authored-By: Artur <83028930+netsvetaev@users.noreply.github.com> * Fixed localization breaking themes * useUpdateTranslation Hook To force trigger translations for data objects * Localize Tab Data * Localize Prompt Input & Current Image Buttons * Localize Gallery & Bug FIxes Fix a bug where the delete image from the context menu wasn't working. Removed tooltips that were broken as they don't work in context menu. * Fix localization breaking in production * Add Toast Localization Support * Localize Unified Canvas * Localize WIP Tabs * Localize Hotkeys * Localize Settings * RU Localization Update Co-Authored-By: Artur <83028930+netsvetaev@users.noreply.github.com> * Add Support for Italian and Portuguese * Localize Toasts * Fix width of language picker items * Localize Backend Messages * Disable Debug Messages * Add Support for French * Fix missing localization for a string in the SettingsModal * Disable French * Styling updates to normalize text and accommodate other langs * Add Portuguese Brazilian * Fix Hotkey headers not being localized. * Fix styling issue on models tag in Settings * Fix Slider Styling to accommodate different languages * Fix slider styling in light mode. * Add German * Add Italian * Add Polish * Update Italian * Localized Frontend Build * Updated RU Translations * Fresh Build with updated RU changes * Bug Fixes and Loc Updates * Updated Frontend Build * Fresh Build Co-authored-by: Artur <83028930+netsvetaev@users.noreply.github.com>
2022-12-24 18:23:21 +00:00
fix(ui): improve IDE TS performance by not resolving JSON The TS Language Server slows down immensely with our translation JSON, which is used to provide kinda-type-safe translation keys. I say "kinda", because you don't get autocomplete - you only get red squigglies when the key is incorrect. To improve the performance, we can opt out of this process entirely, at the cost of no red squigglies for translation keys. Hopefully we can resolve this in the future. It's not clear why this became an issue only recently (like past couple weeks). We've tried rolling back the app dependencies, VSCode extensions, VSCode itself, and the TS version to before the time when the issue started, but nothing seems to improve the performance. 1. Disable `resolveJsonModule` in `tsconfig.json` 2. Ignore TS in `i18n.ts` when importing the JSON 3. Comment out the custom types in `i18.d.ts` entirely It's possible that only `3` is needed to fix the issue. I've tested building the app and running the build - it works fine, and translation works fine.
2023-06-29 01:24:20 +00:00
// import 'i18next';
feat(ui): migrate theming to chakra ui
2023-03-06 09:02:40 +00:00
fix(ui): improve IDE TS performance by not resolving JSON The TS Language Server slows down immensely with our translation JSON, which is used to provide kinda-type-safe translation keys. I say "kinda", because you don't get autocomplete - you only get red squigglies when the key is incorrect. To improve the performance, we can opt out of this process entirely, at the cost of no red squigglies for translation keys. Hopefully we can resolve this in the future. It's not clear why this became an issue only recently (like past couple weeks). We've tried rolling back the app dependencies, VSCode extensions, VSCode itself, and the TS version to before the time when the issue started, but nothing seems to improve the performance. 1. Disable `resolveJsonModule` in `tsconfig.json` 2. Ignore TS in `i18n.ts` when importing the JSON 3. Comment out the custom types in `i18.d.ts` entirely It's possible that only `3` is needed to fix the issue. I've tested building the app and running the build - it works fine, and translation works fine.
2023-06-29 01:24:20 +00:00
// import en from '../public/locales/en.json';
// declare module 'i18next' {
// // Extend CustomTypeOptions
// interface CustomTypeOptions {
// // Setting Default Namespace As English
// defaultNS: 'en';
// // Custom Types For Resources
// resources: {
// en: typeof en;
// };
// // Never Return Null
// returnNull: false;
// }
// }
export default {};
Reference in New Issue Copy Permalink