chore: january 1st release

[AndlerRL]

Changelog:

• [masterbots.ai] feat: onboarding bot profile variants  #324
• fix: hasura thread delete + user dup permissions #330
• [hasura] fix: thread delete and user permissions duplicate #331
• New sonner #334
• Make OG Image API dynamic to be useful without thread ID #335
• Refactor: prelaunch UX/UI Changes #336
• Standardize url building using urlbuilders utility #341
• document hook useSonner #343

Summary by Sourcery

Add support for following chatbots and users.

New Features:

• Introduce user and chatbot following feature.

Tests:

• Update tests to cover new following functionality.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request includes changes to the hasura service to support new features and bug fixes. It also includes changes to the user card component to support following and unfollowing users.

Sequence diagram for user follow/unfollow flow

sequenceDiagram
    participant User
    participant UI
    participant HasuraService
    participant DB

    User->>UI: Click Follow/Unfollow button
    UI->>HasuraService: userFollowOrUnfollow(followerId, followeeId, jwt)
    HasuraService->>DB: Check follow status
    DB-->>HasuraService: Return follow status
    alt Not Following
        HasuraService->>DB: Insert follow relationship
        DB-->>HasuraService: Confirm follow
        HasuraService-->>UI: Return {success: true, follow: true}
    else Already Following
        HasuraService->>DB: Delete follow relationship
        DB-->>HasuraService: Confirm unfollow
        HasuraService-->>UI: Return {success: true, follow: false}
    end
    UI-->>User: Update UI state

Loading

Entity relationship diagram for social following feature

erDiagram
    User ||--o{ SocialFollowing : "has"
    SocialFollowing }o--|| User : "follows"
    SocialFollowing }o--|| Chatbot : "follows"

    User {
        string userId PK
        string username
        string email
        string profilePicture
    }

    SocialFollowing {
        string followerId FK
        string followeeId FK
        number followeeIdChatbot FK
        string createdAt
    }

    Chatbot {
        number chatbotId PK
        string name
        string avatar
    }

Loading

Class diagram for updated Hasura service types

classDiagram
    class HasuraService {
        +getHasuraClient(params: GetHasuraClientParams)
        +getCategories()
        +getCategory(categoryId: number)
        +getChatbots(params: GetChatbotsParams)
        +getThreads(params: GetThreadsParams)
        +getThread(params: GetThreadParams)
        +saveNewMessage(params: SaveNewMessageParams)
        +upsertUser(params: UpsertUserParams)
        +userFollowOrUnfollow(params: FollowParams)
        +chatbotFollowOrUnfollow(params: FollowParams)
    }

    class SocialFollowing {
        +followerId: string
        +followeeId: string
        +followeeIdChatbot: number
        +createdAt: string
    }

    class User {
        +userId: string
        +username: string
        +email: string
        +profilePicture: string
        +followers: SocialFollowing[]
        +following: SocialFollowing[]
    }

    User -- SocialFollowing
    HasuraService -- User

Loading

File-Level Changes

Change	Details	Files
Added support for following and unfollowing users and chatbots.	Added userFollowOrUnfollow function to handle following and unfollowing users. Added chatbotFollowOrUnfollow function to handle following and unfollowing chatbots. Added getFollowStatus function to check if a user is following another user. Added getChatbotFollowStatus function to check if a user is following a chatbot. Added followUser function to follow a user. Added unfollowUser function to unfollow a user. Added followChatbot function to follow a chatbot. Added unfollowChatbot function to unfollow a chatbot.	apps/masterbots.ai/services/hasura/hasura.service.ts
Updated the getBrowseThreads function to support filtering by followed users and chatbots.	Added followedUserId parameter to getBrowseThreads function. Modified the query to filter threads based on whether they are from followed users or chatbots. Added logic to interweave followed and organic threads.	apps/masterbots.ai/services/hasura/hasura.service.ts
Updated the getUserBySlug function to include follower and following information.	Added followers and following fields to the getUserBySlug query.	apps/masterbots.ai/services/hasura/hasura.service.ts
Updated the getCategories function to include chatbot followers.	Added followers field to the chatbot query in getCategories function.	apps/masterbots.ai/services/hasura/hasura.service.ts
Updated the user card component to support following and unfollowing users.	Added a follow/unfollow button to the user card. Added logic to handle following and unfollowing users. Added logic to display the number of followers and following. Added logic to update the user card when a user is followed or unfollowed.	apps/masterbots.ai/components/routes/profile/user-card.tsx
Updated the sidebar link component to support different route types.	Added logic to determine the route type based on the pathname. Added logic to apply different styles based on the route type.	apps/masterbots.ai/components/layout/sidebar/sidebar-link.tsx

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
masterbots	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 22, 2025 1:53am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[sourcery-ai]

Hey @AndlerRL - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding documentation for the new social features and database schema changes to help other developers understand the system
• Standardize the styling approach across components - either use direct Tailwind classes or the cn() utility consistently, but not both

Here's what I looked at during the review

• 🟡 General issues: 5 issues found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟡 Complexity: 1 issue found
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion (bug_risk): Consider using a database transaction to prevent race conditions in follow/unfollow operations

The current implementation could lead to inconsistencies if multiple follow/unfollow requests are made simultaneously. Consider wrapping the status check and follow/unfollow operation in a single database transaction.

Suggested implementation:

  const client = getHasuraClient({ jwt })
  try {
    // Start a transaction
    const result = await client.transaction(async (tx) => {
      const isFollowing = await getFollowStatus(tx, followerId, followeeId)
      if (!isFollowing) {
        await followUser(tx, followerId, followeeId)
        return { success: true, follow: true }
      }
      await unfollowUser(tx, followerId, followeeId)
      return { success: true, follow: false }
    })
    return result

This change assumes that:

1. The Hasura client supports transactions (most GraphQL clients do)
2. The getFollowStatus, followUser, and unfollowUser functions need to be updated to accept a transaction object instead of the client
3. You may need to adjust the transaction API syntax based on your specific Hasura client implementation

[sourcery-ai]

suggestion (bug_risk): Add cleanup for loading states in useEffect

Consider adding cleanup in the useEffect to reset loading states if the component unmounts during data fetching.

Suggested implementation:

  // biome-ignore lint/correctness/useExhaustiveDependencies: <explanation>
  useEffect(() => {
    const abortController = new AbortController();
    let isSubscribed = true;

    const fetchData = async () => {
      setIsLoading(true)
      try {
        if (!activeCategory) {
          await getThreadNum()
        } else {
          await getCategoryName()
        }
        if (isSubscribed) {
          setIsLoading(false)
        }
      } catch (error) {
        if (error.name === 'AbortError') {
          return;
        }
        console.error('Error fetching data:', error)
        if (isSubscribed) {
          setIsLoading(false)
        }
      }
    }

    fetchData()

    return () => {
      isSubscribed = false;
      abortController.abort();
      setIsLoading(false);
    }

The getThreadNum and getCategoryName functions should be updated to accept and use the AbortController's signal in their fetch operations. For example:

const getThreadNum = async (signal?: AbortSignal) => {
  const response = await fetch(url, { signal });
  // ... rest of the function
}

The same should be done for getCategoryName function.

[sourcery-ai]

issue: Add validation for startIndex before calculating endIndex

When startIndex is -1, the endIndex calculation could lead to incorrect substring extraction. Consider adding a guard clause to handle this case explicitly.

[sourcery-ai]

suggestion (bug_risk): Consider preserving original error details instead of using a generic message

The generic error message makes debugging harder. Consider including the original error details in the thrown error message: throw new Error(Failed to fetch thread: ${error.message})

Suggested change

	} catch (error: any) {
	throw new Error('Unknown error occurred while fetching thread')
	} catch (error: any) {
	throw new Error(`Failed to fetch thread: ${error.message}`)

[sourcery-ai]

issue (performance): Toast duration of 15 minutes seems excessive for notifications

Consider using a more standard duration like 3000-5000ms for notifications to avoid them staying on screen too long

[sourcery-ai]

issue (complexity): Consider extracting the profile picture upload and bio generation logic into custom hooks to improve maintainability and testability.

The component has grown complex with multiple responsibilities. Consider extracting the profile picture upload and bio generation logic into custom hooks:

// useProfilePicture.ts
export function useProfilePicture(user: User | null) {
  const [picture, setPicture] = useState(user?.profilePicture)
  const [isUploading, setIsUploading] = useState(false)
  const { uploadFilesCloudinary } = useUploadImagesCloudinary()
  const { updateUserInfo } = useProfile()

  const handleUpload = async (file: File) => {
    setIsUploading(true)
    try {
      const { data, success } = await uploadFilesCloudinary(file)
      if (success) {
        const imageUrl = data?.secure_url as string
        await updateUserInfo(null, null, imageUrl)
        setPicture(imageUrl)
      }
    } finally {
      setIsUploading(false) 
    }
  }

  return { picture, isUploading, handleUpload }
}

// useBioGeneration.ts
export function useBioGeneration(user: User | null) {
  const [bio, setBio] = useState(user?.bio)
  const [isLoading, setIsLoading] = useState(false)
  const { append } = useChat(/* chat config */)

  const generateBio = async () => {
    setIsLoading(true)
    try {
      // Bio generation logic
    } finally {
      setIsLoading(false)
    }
  }

  return { bio, isLoading, generateBio }
}

This separates concerns while maintaining functionality, making the component easier to maintain and test.

[AndlerRL]

@AnoukRImola -- we need to test all these changes to ensure the integrity of this ASAP. Review the recent merged PRs (listed in the changelog) to test them 👀 we need the report to account the progress with the MB development. Merging!

cc - @merivercap

[AndlerRL]

@coderabbitai please elaborate a product update document for the recent changes going to production.

Product Update Example:

What’s shipping 🌟

---

Tip: Use this space to announce features and releases that impact cross-functional stakeholders in your organization like sales or customer support. Avoid listing out every single bug or feature the team worked on.

For team members who want to learn more about a specific release, you can link inline to existing Notion pages by typing @[page title]. Sharing those additional details like project timelines, statuses, and DRIs helps build transparency and create an environment that encourages knowledge sharing.

• Deeply nested sub-pages load 50% faster! Notion supports an infinite hierarchy — that means you can store pages inside pages, inside pages, inside pages, forever. Thanks to a few under-the-hood improvements, these pages now load and save over 50% faster. 57%, to be exact! See more here → [Sub-page load time](https://www.notion.so/Sub-page-load-time-14b9d1881dc181c897ebdf8c3a7eb0ee?pvs=21).
• Create views from existing databases. You’ll see a new option to select a data source whenever you add a new view, allowing you to embed custom synced copies of existing databases in your workspace. Check out [Better databases](https://www.notion.so/Better-databases-14b9d1881dc18191a8d4d4273034d037?pvs=21) for more details!

Announcements 📣

---

Tip: This is a good place to announce upcoming large features, status updates, or even significant delays are good ones to call out. Reference other Notion pages to provide more context on these announcements like the examples below.

• We’ve pushed back the [Database permissions launch](https://www.notion.so/Database-permissions-launch-14b9d1881dc18156860ef4810cad8ebb?pvs=21) date — but we’re still finishing the engineering work required. We’re looking forward to launching the ‣ that prevents accidental edits to the database’s structure — views, filters, property names, property types & more!
• Were you hoping for [Better text editing & copy/paste](https://www.notion.so/Better-text-editing-copy-paste-14b9d1881dc181c981dfd24702760e75?pvs=21)? If so, we’ve got great news — starting this April 8, 2022 it’ll be live on dev. Notion’s text editor has been completely retooled to combine the flexibility of “blocks” with the familiar feeling of a traditional word processor.

FYI’s 📌

---

Tip: The space below should be used for highlighting important team processes or org changes that may have been missed. Don’t forget to link to relevant docs that help drive clarity around why those decisions were made.

• [Bug bash](https://www.notion.so/Bug-bash-14b9d1881dc18131b7d9f4813d36864b?pvs=21) week is April 4, 2022 → April 8, 2022! Please check out the [April ‘22 Bug Bash](https://www.notion.so/April-22-Bug-Bash-14b9d1881dc1814db992fdcf416b5d62?pvs=21) page where you can learn about the bug bash, sign-up for a team or submit tasks for consideration.
• If you’re wondering how we do releases at Notion — please read these RFCs: One focuses on team responsibility and process → [RFC: Release management team](https://www.notion.so/RFC-Release-management-team-14b9d1881dc181df83c8deec7de6b1cb?pvs=21) and the other focuses on technical and tooling improvement → [RFC: Releases](https://www.notion.so/RFC-Releases-14b9d1881dc181f9bd33dcddc232f332?pvs=21) ... and if you want to see more of what we’re kicking off, you can always find it at #rfcs.
• We’re building out a separate mobile team. You might hear some new terms being thrown around, so @Sohrab Amin’s written a bit more about the change here: [New mobile team](https://www.notion.so/New-mobile-team-14b9d1881dc18157a513e91e41eaeaa2?pvs=21).

Launch calendar

** Tip:** Embed a calendar view of the product roadmap directly in your weekly product update so cross-functional teams can see for themselves when a feature is shipping. Link your launch calendar by typing /linked learn more about linked databases [here](https://www.notion.so/help/guides/using-linked-databases).

↓ Click Launch calendar to create and see other views. Filter by project status, team and more!

[Untitled](https://www.notion.so/14b9d1881dc18198887cfb419549ac8b?pvs=21)

Archive 🗂️

---

Tip: Save all your previous updates by storing them in a toggle. Type /toggle, add the date as the toggle header and click it to expand. Finally, drag old updates inside the toggle.

• April 4, 2022

  Add your previous weekly product updates here...

• March 28, 2022

  Add your previous weekly product updates here...

• March 21, 2022

  Add your previous weekly product updates here...

⚠️ **Warning:** Deleting this callout block will delete all references of the pages in the toggle below. ****We use the toggle to store placeholder docs that are used in this template. The placeholder docs don’t contain any valuable content and are used to show the templates functionality.

• Template Placeholder docs

  [New mobile team](https://www.notion.so/New-mobile-team-14b9d1881dc18157a513e91e41eaeaa2?pvs=21)

  [Bug bash](https://www.notion.so/Bug-bash-14b9d1881dc18131b7d9f4813d36864b?pvs=21)

  [April ‘22 Bug Bash](https://www.notion.so/April-22-Bug-Bash-14b9d1881dc1814db992fdcf416b5d62?pvs=21)

  [RFC: Release management team](https://www.notion.so/RFC-Release-management-team-14b9d1881dc181df83c8deec7de6b1cb?pvs=21)

  [RFC: Releases](https://www.notion.so/RFC-Releases-14b9d1881dc181f9bd33dcddc232f332?pvs=21)

  [Launch calendar](https://www.notion.so/14b9d1881dc181e7913cf83794255c84?pvs=21)

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@AndlerRL Here's the product update document for the January 1st release:

What's shipping 🌟

• Enhanced User Onboarding Experience! We've introduced new bot profile variants with an improved onboarding flow, making it easier for new users to discover and interact with chatbots. The new system includes mobile-optimized views and responsive layouts for a seamless experience across all devices.

• Improved Notification System We've upgraded our notification system to Sonner, providing a more polished and consistent way to display system messages, alerts, and feedback to users. This enhancement brings better visibility and improved user interaction feedback throughout the platform.

• Dynamic Open Graph Image Generation Our sharing capabilities have been enhanced with a new dynamic OG image generation system. This improvement means better social media previews when sharing content from the platform, with or without specific thread contexts.

Announcements 📣

• Pre-launch UI/UX Refinements We've implemented significant improvements to the platform's interface, including:

  • Enhanced mobile responsiveness for chat and browse sections
  • Refined navigation experience in header and sidebar
  • Improved route-based UI customization for better context awareness

• Backend Stability Improvements We've resolved several backend issues related to thread management and user permissions, ensuring a more reliable platform experience.

FYI's 📌

• URL Structure Standardization We've implemented a standardized URL building system across the platform, ensuring consistent and reliable navigation patterns.

• Documentation Updates Our development documentation has been enhanced with detailed JSDoc comments for key components, improving maintainability and developer experience.

Launch calendar

• January 1st, 2025: Platform-wide release including all mentioned features and improvements

🔗 Analysis chain

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Fetch details for each PR in the changelog
for pr in 324 330 331 334 335 336 341 343; do
  echo "=== PR #$pr ==="
  gh pr view $pr --repo bitcashorg/masterbots
  echo
done

Length of output: 14405