Fix Update button disabled when clearing optional tenantID in Microsoft OAuth

[Copilot]

The Update button becomes disabled when clearing the tenantID field in Microsoft OAuth settings, preventing users from removing an optional tenant configuration.

Root Cause

The reactive secret statement required both clientSecret and tenantID to be truthy before constructing a new secret. When tenantID is cleared, the condition fails and secret reverts to provider.secret, making the component think nothing changed.

// Before: Both fields required for new secret
$: secret = clientSecret && tenantID 
    ? JSON.stringify({ clientSecret, tenantID }) 
    : provider.secret;

// After: tenantID is optional
$: secret = clientSecret
    ? JSON.stringify({ clientSecret, ...(tenantID && { tenantID }) })
    : provider.secret;

Changes

• Use spread operator to conditionally include tenantID only when present
• Clearing tenantID now produces { clientSecret } instead of reverting to original secret
• Update button correctly detects the change and enables

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• o1.ingest.sentry.io
  • Triggering command: node (vitest) (dns block)
  • Triggering command: node build.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

On microsoftOAuth.svelte, When someone has tenantID set and then they try to delete it, the Update button becomes disabled.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Sites support three domain rule types: Active deployment, Git branch, and Redirect

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}