Skip to content

Conversation

@bakatrouble
Copy link

@bakatrouble bakatrouble commented Aug 27, 2025

ditto.

Summary by Sourcery

Add a notifications boolean field to the User class and retain legacy data for future use

New Features:

  • Introduce a notifications attribute on User to reflect legacy notification settings

Enhancements:

  • Preserve the entire legacy data payload in a new _legacy attribute

Summary by CodeRabbit

  • New Features
    • User objects now include a notifications boolean attribute indicating whether notifications are enabled for the user. When legacy data is unavailable, it defaults to False.
  • Documentation
    • Updated the User class documentation to describe the new notifications attribute, including its purpose and default behavior for improved discoverability and clarity for developers using the API.

@sourcery-ai
Copy link

sourcery-ai bot commented Aug 27, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The User class now retains the full legacy data and exposes a new notifications flag initialized from the legacy payload.

Class diagram for updated User class with notifications field

classDiagram
    class User {
        - _client: Client
        - _legacy: dict
        id: str
        created_at: str
        notifications: bool
        ...
    }
Loading

File-Level Changes

Change Details Files
Persist legacy data dictionary on the User instance
  • Assign legacy dict to self._legacy with a type annotation
twikit/user.py
Add notifications attribute to User model
  • Extend class docstring to describe notifications
  • Initialize self.notifications from legacy.get('notifications', False)
twikit/user.py

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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 27, 2025

Walkthrough

Adds a new public boolean attribute notifications to User, sourced from legacy data, and stores the entire legacy dict in a new internal field _legacy. Updates the User class docstring accordingly. No other methods or control flow are changed.

Changes

Cohort / File(s) Summary
User model update
twikit/user.py
Add public attribute notifications: bool initialized from legacy.get('notifications', False); introduce internal _legacy: dict to store legacy data; update class docstring to document notifications.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I twitch my ears at legacy tales,
A bool now hops from dusty trails—
Notifications blink, a gentle ping,
In _legacy’s burrow, we stash the thing.
With one small hop, the model’s bright—
Carrots saved, alerts in sight! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
twikit/user.py (3)

87-88: Clarify semantics; consider Optional when API omits this field

Legacy often omits notifications. Treating absence as False can mislead consumers.

Apply this docstring tweak:

-    notifications : :class:`bool`
-        Indicates if notifications were enabled for this user.
+    notifications : Optional[:class:`bool`]
+        Whether notifications are enabled for this user relative to the authenticating account. None if not provided by the API.

94-94: Defensive copy for _legacy to avoid accidental external mutation

Store a shallow copy; annotate precisely.

-        self._legacy: dict = legacy
+        self._legacy: dict[str, Any] = legacy.copy()

Add missing import:

-from typing import TYPE_CHECKING, Literal
+from typing import TYPE_CHECKING, Literal, Any

129-129: Preserve “unknown” vs “false” in notifications
After searching for all .notifications references, the only occurrence is its initialization in twikit/user.py (line 129), so there are no downstream boolean‐only assumptions that would break:

• twikit/user.py:129 – drop the default False and widen the annotation to allow None for “not provided by API.”

Recommended diff:

-        self.notifications: bool = legacy.get('notifications', False)
+        self.notifications: bool | None = legacy.get('notifications')
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3b18105 and f001531.

📒 Files selected for processing (1)
  • twikit/user.py (2 hunks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant