Migration to Golang

[shahank42]

This PR completely changes the fundamental working model of this application.

Where do I even begin.

Previously, TextPilot was using an end-to-end typescript monorepo setup where the client and server communicated via. a REST API abstracted using oRPC. For the WhatsApp stuff we used whatsapp-web.js which for every connected client ran a Puppeteer instance.

After a lot of deliberation, it was decided that TextPilot would be shifting off of whatsapp-web.js in favor of using Whatsmeow: a Golang based library which communicated with WhatsApp Web directly via. the API rather than initializing a headless browser instance. This decision was made to keep the entire app easy to package (Puppeteer demanded we ship Chromium with the binaries) and (in the future) deploy to a VPS for use with multiple clients.

Naturally this meant the entire backend and communication logic had to be re-written using Golang. And that's exactly what I did (well to be fair Gemini 2.5 Flash helped a ton). Instead of working upon the existing code, I decided it was better to start completely from scratch. So far things are looking pretty good.

Features that work

• Multiple client log in (which was previously not possible, or it was but it wasn't like viable)
• Chat selection
• Read messages from chats
• Messaging

Features that don't work (yet)

• Message quoting
• Displaying quoted messages

Known bugs/Untested parts

• Multiple SSE event listeners fired (biggest bug)
• Status broadcasts being mistaken for chats
• Rendering non-text messages

I'm currently developing this branch, we'll see where it goes from there. Currently the whole thing needs a major refactor, because it's pretty disorganized as it stands.

Discussions and contributions are always welcome!

[coderabbitai]

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

48 files out of 166 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits.

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

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Warning

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

43 files out of 161 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits.