feat: add DISABLE_ANONYMOUS_USER_CREATE_EMAIL which only allow logi…

[dreamhunter2333]

User description

…n user create email address

#540

---

PR Type

Enhancement, Documentation

---

Description

• Add DISABLE_ANONYMOUS_USER_CREATE_EMAIL configuration option

• Update frontend logic to respect new configuration

• Update API endpoints to enforce new configuration

• Document new configuration in CLI documentation

---

Changes walkthrough 📝

	Relevant files
Enhancement	8 files Login.vue Add logic to conditionally show email creation tab              +11/-3    worker_config.ts Add `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` to worker config +1/-0      commom_api.ts Include `disableAnonymousUserCreateEmail` in open API settings +1/-0      index.ts Enforce `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` in new address endpoint +5/-0      types.d.ts Add `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` to type definitions +1/-0      index.js Fetch `disableAnonymousUserCreateEmail` setting from API  +1/-0      index.js Add `disableAnonymousUserCreateEmail` to global state        +1/-0      wrangler.toml.template Add `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` to wrangler template +2/-0
Documentation	3 files CHANGELOG.md Document new feature in changelog                                                +1/-0      cli.md Document `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` in English CLI docs +2/-0      worker.md Document `DISABLE_ANONYMOUS_USER_CREATE_EMAIL` in Chinese CLI docs +2/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 540 - Fully compliant Fully compliant requirements: Prevent abuse by requiring users to register before creating email addresses. Implement a configuration option to disable anonymous email creation. Update frontend and backend logic to respect this new configuration. Document the new configuration option. Not compliant requirements: None

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Issue Ensure that the showNewAddressTab computed property correctly handles all edge cases where anonymous users should not be able to create email addresses. const showNewAddressTab = computed(() => { if (openSettings.value.disableAnonymousUserCreateEmail && !userSettings.value.user_email ) { return false; } return openSettings.value.enableUserCreateEmail; });

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add optional chaining to prevent runtime errors when accessing properties of potentially undefined objects Ensure that openSettings.value and userSettings.value are properly initialized before accessing their properties to avoid potential runtime errors. frontend/src/views/common/Login.vue [188-189] -if (openSettings.value.disableAnonymousUserCreateEmail - && !userSettings.value.user_email +if (openSettings.value?.disableAnonymousUserCreateEmail + && !userSettings.value?.user_email ) { Suggestion importance[1-10]: 8 Why: This suggestion adds optional chaining to prevent potential runtime errors if openSettings.value or userSettings.value are undefined. This is a valuable improvement for ensuring code robustness.	8