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

Add explanation for initialRoot usage in Documentation #173

Merged
merged 2 commits into from
Oct 25, 2024

Conversation

raararaara
Copy link
Contributor

@raararaara raararaara commented Oct 24, 2024

What this PR does / why we need it?

This PR adds documentation to describe the new feature that allows setting initial values when attaching a document. This functionality was introduced in PR #986, enabling developers to initialize documents with specific values upon attachment.

Any background context you want to provide?

What are the relevant tickets?

Fixes #

Checklist

  • Added relevant tests or not required
  • Didn't break anything

Summary by CodeRabbit

  • Documentation
    • Updated the Yorkie JS SDK documentation with a new section on initializing the root of a Document, detailing management of application data types.
    • Clarified how initial values are applied based on existing keys and provided examples for better understanding.
    • Emphasized that elements added by initialRoot are applied locally and not sent to the server during the attach process.

@CLAassistant
Copy link

CLAassistant commented Oct 24, 2024

CLA assistant check
All committers have signed the CLA.

Copy link

coderabbitai bot commented Oct 24, 2024

Walkthrough

The documentation for the Yorkie JS SDK has been updated to include a new section on initializing the root of a Document. This section explains how to manage application data types using the initialRoot option during the Document.attach() method. It details the behavior of initial values based on key existence and clarifies that elements added by initialRoot are applied locally and not sent to the server during the attach process. The overall structure of the documentation remains unchanged.

Changes

File Change Summary
docs/js-sdk.mdx Added a new section on "Initializing root" detailing the use of the initialRoot option in Document.attach(), including behavior regarding existing keys and local application of values.

Poem

In the land of code where rabbits play,
A new section blooms to brighten the day.
With initialRoot to guide our way,
We manage our data, come what may!
So hop along, let’s code and cheer,
For every new change brings us near! 🐇✨


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.

@hackerwins hackerwins marked this pull request as ready for review October 25, 2024 02:00
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 (4)
docs/js-sdk.mdx (4)

70-77: Add resulting state comment for clarity.

Consider adding a comment showing the resulting state after initialization to help readers understand the outcome.

 await client.attach(doc, {
   initialRoot: {
     list: [1, 2, 3],
     counter: new yorkie.Counter(yorkie.IntType, 0),
   },
 });
+// resulting state
+// root = {
+//   list: [1, 2, 3],
+//   counter: 0
+// }

84-96: Fix code indentation for consistency.

The indentation in the code example should be consistent with other examples in the documentation.

-await client.attach(doc, {
-  initialRoot: {
-    list: [],
-  },
-});
+await client.attach(doc, {
+    initialRoot: {
+        list: [],
+    },
+});

-// Another client tries to attach with initialRoot option:
-await client.attach(doc, {
-  initialRoot: {
-    list: [1, 2, 3],    // this update will be discarded
-    counter: new yorkie.Counter(yorkie.IntType, 0), // this update will be applied
-  },
-});
+// Another client tries to attach with initialRoot option:
+await client.attach(doc, {
+    initialRoot: {
+        list: [1, 2, 3],    // this update will be discarded
+        counter: new yorkie.Counter(yorkie.IntType, 0), // this update will be applied
+    },
+});

105-106: Consider expanding supported types information.

The reference to supported types could be more specific by listing the primitive types that are supported.

-We support element types for Primitives, and [Custom CRDT types](/js-sdk/#custom-crdt-types/).
+We support element types for Primitives (string, number, boolean, null), and [Custom CRDT types](/js-sdk/#custom-crdt-types/).

107-110: Enhance warning with implications.

The warning about local application could be clearer about its implications for application developers.

-Elements added by `initialRoot` are not sent to the server during the `attach` process. They are applied locally to the Document after push-pull during `attach`.
+Elements added by `initialRoot` are not sent to the server during the `attach` process. They are applied locally to the Document after push-pull during `attach`. This means other clients will not receive these initial values until they explicitly attach to the document.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b500581 and a1603cc.

📒 Files selected for processing (1)
  • docs/js-sdk.mdx (1 hunks)
🔇 Additional comments (1)
docs/js-sdk.mdx (1)

66-68: LGTM! Clear and concise introduction.

The introduction effectively explains the purpose of initialRoot and its relationship to managing application data.

Copy link
Member

@hackerwins hackerwins left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution.

@hackerwins hackerwins merged commit 9331298 into yorkie-team:main Oct 25, 2024
2 checks passed
@raararaara raararaara deleted the initial-root-doc branch October 25, 2024 09:36
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