## Summary - Improved Korean translations with natural terms for e-commerce context - Applied consistent translations throughout the admin interface - Added all missing required keys for i18n validation ## Changes - Used appropriate e-commerce terms: "재고 키트" → "구성 상품", "이행" → "주문 처리/배송 준비" - Applied consistent translation: "항목" → "상품" throughout the file - Distinguished shipping states: "markAsShipped" (발송 완료), "markAsDelivered" (배송 완료) - Added missing required keys for products, inventory, orders, taxRegions, and promotions - All i18n validations now pass ## Test plan - [x] Run `yarn i18n:validate ko.json` - passes validation - [x] Verify translations are contextually appropriate for e-commerce - [x] Ensure consistency across all admin interface sections 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: William Bouchard <46496014+willbouch@users.noreply.github.com>
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:
- Configure the top-level
parserOptionsproperty like this:
export default {
// other rules...
parserOptions: {
ecmaVersion: 'latest',
sourceType: 'module',
project: ['./tsconfig.json', './tsconfig.node.json'],
tsconfigRootDir: __dirname,
},
}
- Replace
plugin:@typescript-eslint/recommendedtoplugin:@typescript-eslint/recommended-type-checkedorplugin:@typescript-eslint/strict-type-checked - Optionally add
plugin:@typescript-eslint/stylistic-type-checked - Install eslint-plugin-react and add
plugin:react/recommended&plugin:react/jsx-runtimeto theextendslist