Add comprehensive i18n documentation#36
Open
konard wants to merge 3 commits intoivansglazunov:mainfrom
Open
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: undefined
|
@konard is attempting to deploy a commit to the ivansglazunov's projects Team on Vercel. A member of the Team first needs to authorize it. |
- Document all i18n features and configuration - Include quick start guide and API reference - Add migration guide for converting components - Document available namespaces and best practices - Include troubleshooting section - Add guide for adding new languages 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Task completed - comprehensive i18n documentation added. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 📎 Log file uploaded as GitHub Gist (293KB) Now working session is ended, feel free to review and add any feedback on the solution draft. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds comprehensive documentation for the i18n (internationalization) implementation in Hasyx, addressing issue #15.
What's Included
Current i18n Implementation Status
The i18n implementation in Hasyx is already complete on the main branch, with:
✅ next-intl integration configured in
next.config.ts✅ Two languages supported: English (en) and Russian (ru)
✅ 661+ translation keys in
i18n/en.json✅ 663+ translation keys in
i18n/ru.json✅ All major components migrated (see
translations.mdchecklist)✅ Client-side locale switching via
LocaleSwitchercomponent✅ Type-safe translations with TypeScript support
✅ Organized namespaces (common, auth, files, messaging, etc.)
Key Features Documented
Configuration
NEXT_PUBLIC_LOCALE)API Reference
useTranslations()- Client-side hook for translationsuseLocale()- Get/set current localegetLocale()- Get default locale from envi18nMessages()- Get all messages for a localeLocaleSwitcher- Component for switching languagesAvailable Namespaces
Developer Guides
Troubleshooting
Files Changed
I18N.md- New comprehensive documentation (401 lines)Testing
The i18n system is already fully functional in the main branch:
useTranslationshooktranslations.mdfor the complete migration checklistDocumentation Access
Users can access the documentation at:
I18N.mdin the root directorytranslations.mdFixes #15
🤖 Generated with Claude Code