Skip to content

Conversation

@jayant-dhingra-cb
Copy link
Contributor

No description provided.

@gemini-code-assist
Copy link

Summary of Changes

Hello @jayant-dhingra-cb, I'm Gemini Code Assist1! 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 updates the documentation for the cbl-reactnative library to align with its 1.0.0 release. The changes focus on introducing new and improved APIs for managing event listeners and logging, alongside a revised approach to replicator configuration. The primary goal is to provide clear, up-to-date guidance for developers, including a dedicated migration guide to facilitate a smooth transition to the new version.

Highlights

  • API Updates for Listeners: Introduced a new ListenerToken API for managing change listeners across collections, documents, queries, and replicators, replacing older removeChangeListener() methods.
  • Enhanced Logging System: Implemented a new LogSinks API for flexible logging control, offering Console, File, and Custom log sinks with configurable levels and domains, deprecating the Database.setLogLevel() method.
  • Replicator Configuration Refinement: Updated the ReplicatorConfiguration API to pass collections directly in the constructor using CollectionConfiguration objects, with the addCollection() method now deprecated.
  • Comprehensive Migration Guide: Added a detailed migration guide for version 1.0.0, outlining breaking changes, deprecated APIs, new features, and step-by-step instructions for updating existing codebases.
  • Documentation Structure Improvements: Reorganized documentation with new 'Guides' and 'Migration' categories, and updated various examples to reflect the latest API usage and best practices.

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

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request provides a comprehensive update to the documentation for the upcoming version 1.0.0 of cbl-reactnative. The changes include a new migration guide, updated release notes, and revised code examples across several documents to reflect the new APIs for logging, replication configuration, and event listeners.

The new documentation is well-structured and the examples are much clearer. I've identified a few areas for improvement:

  • There's an inconsistent use of Docusaurus admonition syntax (:::: vs :::). I've left comments to correct this to ensure proper rendering.
  • One of the code examples uses a magic number instead of an enum constant, which could be improved for clarity.

Overall, this is a great update that will be very helpful for developers migrating to or starting with version 1.0.0.

}

// Check activity level
if (change.status.getActivityLevel() === 3) { // IDLE

Choose a reason for hiding this comment

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

medium

For better readability and to avoid magic numbers, it's recommended to use the ReplicatorActivityLevel.IDLE enum member instead of the raw value 3. This makes the code clearer and less prone to errors if the enum values ever change. You'll also need to add ReplicatorActivityLevel to the import statement from cbl-reactnative.

Suggested change
if (change.status.getActivityLevel() === 3) { // IDLE
if (change.status.getActivityLevel() === ReplicatorActivityLevel.IDLE) { // IDLE

@jayant-dhingra-cb jayant-dhingra-cb merged commit 5cf6749 into main Jan 12, 2026
4 checks passed
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.

3 participants