Smart JID validation, Session UI controls & Local Dev Infrastructure

[lomeliDev]

This PR introduces significant improvements to the core message handling, extends the Dashboard UI, and enhances the local development environment with Docker.

🚀 Key Changes

1. Backend & Core Logic
   Smart JID Validation: Implemented a robust validation mechanism using IsOnWhatsApp.

Fix: Automatically corrects regional JID formats before sending messages. This specifically resolves issues with Mexican numbers (converting +52 to +521 when required by WhatsApp) and prevents sending messages to non-existent numbers.

New Endpoint (POST /misc/phone): Added a utility endpoint to validate and format phone numbers (returns the correct JID and existence status) without sending a message.

Code Cleanup: Fixed variable shadowing in handlers.go (MarkRead) and standardized logging to use zerolog for better consistency.

2. Frontend (Dashboard)
   Session Management: Added a new "Session" widget section to the Dashboard.

Features: UI cards for Connect, Disconnect, and Logout.

UX: Implemented Semantic UI confirmation modals and toast notifications for success/error states.

Logic: Javascript functions now properly handle auth tokens and interact with /session/* endpoints.

3. Infrastructure (Docker)
   Local S3 (MinIO): Added a minio service to docker-compose.yml (ports 9000/9001) to facilitate local testing of S3 media storage.

Proxy Testing: Added proxy-http (TinyProxy) and proxy-socks (Go-Socks5) services to the compose file to allow easy testing of WuzAPI's proxy configurations in a local environment.

Env Variables: Updated environment configuration to support these new services (RabbitMQ, MinIO, Adminer).

🧪 How to Test
Phone Validation:

POST to /misc/phone with a payload like {"phone": "521234567890"}.

Response should return the corrected JID (e.g., adding the '1' for Mexico if needed) and exists: true.

Dashboard:

Go to /dashboard.

Use the new Session cards to Disconnect and Reconnect the session.

Docker Infra:

Run docker-compose up -d minio proxy-http.

Verify MinIO console at http://localhost:9001.

📸 Screenshots

Checklist
[x] Code compiles correctly

[x] New endpoint /misc/phone tested

[x] Dashboard UI functional

[x] Docker containers build and run

[gemini-code-assist]

Summary of Changes

Hello @lomeliDev, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the application's core messaging capabilities by introducing intelligent phone number validation and formatting, improving the reliability of message delivery. It also expands the administrative dashboard with new session control features, offering a more intuitive user experience. Furthermore, the local development environment has been substantially upgraded with additional Docker services, streamlining the testing of various system components like S3 storage and proxy configurations.

Highlights

• Smart JID Validation: Implemented a robust validation mechanism using IsOnWhatsApp to automatically correct regional JID formats (e.g., adding '1' for Mexican numbers) and prevent sending messages to non-existent numbers. This new validation logic is integrated across various message handling functions.
• New Phone Validation Endpoint: Added a new utility endpoint POST /misc/phone that allows validating and formatting phone numbers, returning the corrected JID and existence status without sending a message.
• Dashboard Session Management UI: Introduced a new 'Session' widget section to the Dashboard UI, providing cards for 'Connect', 'Disconnect', and 'Logout' actions. These actions are supported by new JavaScript functions that handle authentication tokens and interact with the /session/* endpoints, complete with Semantic UI confirmation modals and toast notifications.
• Enhanced Local Development Infrastructure: Expanded the docker-compose.yml configuration to include new services for local development and testing: MinIO (for S3 media storage), Adminer (for database management), a Webhook Tester, an HTTP proxy (TinyProxy), and a SOCKS5 proxy (Go-Socks5). Environment variables in .env.sample were updated to support these new services.
• Core Logic Refinements: Fixed variable shadowing in handlers.go (specifically in MarkRead) and standardized logging to use zerolog for improved consistency and structured logging.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces valuable features, including smart JID validation, new session management controls in the UI, and a significantly improved local development infrastructure with Docker. The backend changes, especially the new validateMessageFields function, are a great step towards more robust message handling. The Docker setup with MinIO and proxies will certainly streamline testing.

I've identified a critical logic bug in the new /misc/phone endpoint's error handling that needs to be addressed. Additionally, there are a few medium-severity issues related to Docker image pinning for reproducibility and misleading error messages. While the PR aimed to standardize logging, I noticed some older logging patterns remain; it would be great to update these for consistency.