mirror of https://github.com/toeverything/AFFiNE.git synced 2026-07-16 09:36:17 +08:00

Files

T

chauhan_s 31101a69e7 fix: Refine verify email dialog for verify and change email flows (#14671 )

### Summary
This PR improves the verify email dialog by giving the verify-email and
change-email flows distinct messaging instead of reusing the same
generic copy.

### What changed
* Use flow-specific body copy in the verify email dialog
* Keep the existing action-specific subtitle behavior for:
  * Verify email
  * Change email
* Update the English i18n strings so each flow explains the correct
intent:
  * Verify email focuses on confirming email ownership
  * Change email focuses on securely starting the email-change process
### Why
The previous dialog message was shared across both flows, which made the
change-email experience feel ambiguous. This update makes the intent
clearer for users and better matches the action they are taking.



https://www.loom.com/share/c64c20570a8242358bd178a2ac50e413


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved clarity in email verification and email change dialog
messages to better explain the confirmation process and link purpose.
* Enhanced distinction between email verification and email change
workflows with context-specific messaging.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-03-17 23:28:16 +08:00

src

fix: Refine verify email dialog for verify and change email flows (#14671 )

2026-03-17 23:28:16 +08:00

.gitignore

refactor(i18n): lazy load languages (#8456 )

2024-10-10 09:03:06 +00:00

.i18n-codegen.json

chore: add monorepo tools (#9196 )

2024-12-24 15:29:48 +08:00

build.ts

feat(core): integrate google calendar sync (#14248 )

2026-01-13 02:38:16 +08:00

cleanup.mjs

chore(i18n): cleanup i18n file (#8318 )

2024-09-20 06:25:17 +00:00

package.json

test: migrate test & utils (#14569 )

2026-03-07 04:12:27 +08:00

README.md

refactor(i18n): new hook api (#7273 )

2024-06-20 02:19:41 +00:00

tsconfig.json

chore(server): stdout is enough for collecting server logging (#9964 )

2025-02-05 13:25:11 +00:00

README.md

i18n

Usages

Update missing translations into the base resources, a.k.a the src/resources/en.json
Replace literal text with translation keys

import { useI18n, LOCALES } from '@affine/i18n';
// src/resources/en.json
// {
//     'Text': 'some text',
//     'Switch to language': 'Switch to {{language}}', // <- you can interpolation by curly brackets
// };

const App = () => {
  const i18n = useI18n();
  const changeLanguage = (language: string) => {
    i18n.changeLanguage(language);
  };

  return (
    <div>
      <div>{i18n['Workspace Settings']()}</div>
      <>
        {LOCALES.map(option => {
          return (
            <button
              key={option.name}
              onClick={() => {
                changeLanguage(option.tag);
              }}
            >
              {option.originalName}
            </button>
          );
        })}
      </>
    </div>
  );
};

How the i18n workflow works?

When the src/resources/en.json(base language) updated and merged to the develop branch, will trigger the languages-sync action.
The languages-sync action will check the base language and add missing translations to the Tolgee platform.
This way, partners from the community can update the translations.

How to sync translations manually

Set token as environment variable

export TOLGEE_API_KEY=tgpak_XXXXXXX

Run the sync-languages:check to check all languages
Run the sync-languages script to add new keys to the Tolgee platform
Run the download-resources script to download the latest full-translation translation resources from the Tolgee platform

README.md

i18n

Usages

How the i18n workflow works?

How to sync translations manually

References