Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove use of ARTRealtimePresence query in public API #65

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

lawrence-forooghian
Copy link
Collaborator

@lawrence-forooghian lawrence-forooghian commented Sep 26, 2024

See comment; the problem described there arose when Marat tried to implement a mock of Presence for #4.

Summary by CodeRabbit

  • New Features

    • Introduced a new PresenceQuery struct to enhance presence management.
    • Updated the get method in the Presence protocol for improved functionality.
  • Bug Fixes

    • Resolved a compiler error related to non-sendable types in the Presence protocol.

See comment; the problem described there arose when Marat tried to
implement a mock of Presence for #4.
Copy link

coderabbitai bot commented Sep 26, 2024

Walkthrough

The changes involve updating the Presence protocol in Presence.swift by modifying the method signature of get(params:) to accept a new PresenceQuery struct instead of the previous ARTRealtimePresenceQuery?. The PresenceQuery struct is defined as a Sendable type and includes properties such as limit, clientID, connectionID, and waitForSync, each with default values. This adjustment addresses a compiler error related to non-sendable types in actor contexts.

Changes

Files Change Summary
Sources/AblyChat/Presence.swift - Updated method signature: func get(params: ARTRealtimePresenceQuery?) to func get(params: PresenceQuery?) in Presence protocol.
- Added new struct: public struct PresenceQuery: Sendable with properties and an internal initializer.

Possibly related PRs

  • Fix Presence.get(…) signature #41: This PR modifies the get(params:) method in the Presence protocol, which is directly related to the changes made in the main PR regarding the method signature and the introduction of the PresenceQuery struct.

Suggested reviewers

  • umair-ably
  • maratal

Poem

🐇 In the code where bunnies play,
A new query hops in today.
With properties neat, and types that send,
Our Presence now has a brand new friend!
So let’s code and cheer, with joy we’ll sway,
For changes that brighten our coding way! 🌟


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
🪧 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 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.

Copy link

@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

🧹 Outside diff range and nitpick comments (2)
Sources/AblyChat/Presence.swift (2)

65-71: Excellent explanation and future-proofing

The detailed comments provide valuable context for the introduction of PresenceQuery and demonstrate a thoughtful approach to addressing Swift concurrency issues. Creating an issue (#64) to revisit this implementation in the future is a great practice for tracking potential improvements.

To enhance the comment further, consider adding a brief explanation of why ARTRealtimePresenceQuery is not Sendable, if known. This could provide additional context for future developers working on this code.


72-84: Approved: Well-structured PresenceQuery implementation

The PresenceQuery struct is well-implemented, addressing the compiler errors related to Sendable types and providing a clear replacement for ARTRealtimePresenceQuery. The properties cover the essential aspects of a presence query, and the use of default values in the initializer provides flexibility for API users.

Consider making the initializer public instead of internal to allow users of your library to create custom PresenceQuery instances more easily. This would enhance the usability of your API without compromising encapsulation.

public init(limit: Int = 100, clientID: String? = nil, connectionID: String? = nil, waitForSync: Bool = true) {
    // ... (rest of the implementation remains the same)
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 83a3542 and 8184232.

📒 Files selected for processing (1)
  • Sources/AblyChat/Presence.swift (2 hunks)
🔇 Additional comments (2)
Sources/AblyChat/Presence.swift (2)

8-8: Approved: Alignment with PR objectives

The change from ARTRealtimePresenceQuery? to PresenceQuery? in the get(params:) method signature aligns well with the PR objective of removing the use of ARTRealtimePresence query in the public API. This modification likely improves type safety and makes the API more Swift-friendly.


Line range hint 1-84: Summary: Successful removal of ARTRealtimePresence query from public API

The changes in this file effectively achieve the PR objective of removing the use of ARTRealtimePresence query from the public API. The introduction of the PresenceQuery struct as a replacement for ARTRealtimePresenceQuery improves type safety and addresses compiler errors related to non-sendable types in actor contexts.

The modifications are well-documented, with detailed comments explaining the rationale behind the changes and considerations for future improvements. The implementation demonstrates a thoughtful approach to Swift concurrency issues and maintains the functionality of the presence query feature.

Overall, these changes enhance the API's usability and maintainability while setting the groundwork for potential future optimizations.

Copy link
Collaborator

@maratal maratal left a comment

Choose a reason for hiding this comment

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

LGTM

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.

2 participants