feat: Add phone number support to ClerkUser state

[supmo668]

Summary

This PR adds phone number support to the ClerkUser state class, enabling applications to access and manage user phone numbers through the Clerk API.

Changes

• Added phone_number and phone_number_id properties to ClerkUser state
• Added update_phone_number method to ClerkUser for updating user phone numbers
• Added update_user_phone_number helper function for use in custom event handlers
• Load phone number data in the load_user event handler

Usage Example

import reflex_clerk_api as clerk

class MyState(rx.State):
    @rx.event
    async def update_my_phone(self) -> EventType:
        # Using the helper function
        new_phone = await clerk.update_user_phone_number(self, '+12025551234')
        return rx.toast.success(f'Phone updated: {new_phone.phone_number}')

Notes

• Phone numbers are stored in E.164 format (e.g., +12025551234)
• The phone_number_id is needed for updating/deleting phone numbers via Clerk API
• When a new phone number is set, the old one is automatically deleted

[Copilot]

Pull request overview

Adds phone number support to the ClerkUser state so apps can read and update a user’s phone number via the Clerk backend API.

Changes:

• Adds phone_number and phone_number_id to ClerkUser and loads them in load_user.
• Introduces ClerkUser.update_phone_number plus a standalone update_user_phone_number helper.
• Adds a GitHub Actions workflow intended to sync a fork with upstream.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 10 comments.

File	Description
custom_components/reflex_clerk_api/clerk_provider.py	Adds phone number fields, loading, and update APIs for Clerk users.
.github/workflows/sync-upstream.yml	Adds an automated upstream sync workflow (not related to phone number support).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[supmo668]

Hey Tim! 👋

Thanks for maintaining this excellent library - we've been using it extensively in our Longevity Clinic project.

I've reviewed the phone number support feature and here's a summary with suggestions:

✅ What's Good

• Clean API design with both ClerkUser.update_phone_number method and standalone update_user_phone_number helper
• Proper E.164 format documentation
• Handles phone creation, update, and deletion flows nicely
• Exports are properly added to __init__.py

📝 Suggestions Based on Copilot Review

I agree with several of Copilot's points:

2. Primary phone selection - The code now correctly looks up the primary phone via primary_phone_number_id before falling back to first in list - this matches the docstring 👍

3. Logging - Consider changing INFO→DEBUG for phone operations to avoid PII in logs, or at least mask the phone number

4. Sync workflow - The .github/workflows/sync-upstream.yml seems unrelated to the phone number feature - might be worth splitting into a separate PR to keep this one focused

📚 Documentation Needs

The docs/features.md should be updated to mention the new phone number properties on ClerkUser:

- **ClerkUser**: Provides access to additional user information like `image_url`, `email_address`, `phone_number`, and `phone_number_id`.

And perhaps a brief example:

# Accessing phone number
clerk_user = await self.get_state(clerk.ClerkUser)
print(clerk_user.phone_number)  # E.164 format: +12025551234

# Updating phone number (from any event handler)
await clerk.update_user_phone_number(self, '+12025551234')

🚀 Overall

This is a solid addition that we're already using in production. Happy to help with any follow-up changes!

• Mo (supmo668)

[TimChild]

Thanks @supmo668! Glad it has been useful to you, and thanks a lot for the PR... Looks great!