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

Update CHANGELOG.md for v0.4.20 #820

Merged
merged 2 commits into from
May 24, 2024
Merged

Update CHANGELOG.md for v0.4.20 #820

merged 2 commits into from
May 24, 2024

Conversation

hackerwins
Copy link
Member

@hackerwins hackerwins commented May 24, 2024

What this PR does / why we need it?

Update CHANGELOG.md for v0.4.20

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

  • New Features

    • Enhanced Tree.toXML to return valid XML.
    • Improved type inference in Document.subscribe.
    • Introduced RHT.GC for better garbage collection.
    • Implemented GCPair for TreeNode and TextNode.
  • Optimizations

    • Optimized syncs in push-only sync mode.
  • Documentation

    • Updated examples version to v0.4.19.
  • Chores

    • Updated package version to 0.4.20.

Copy link

coderabbitai bot commented May 24, 2024

Warning

Rate Limit Exceeded

@hackerwins has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 37 minutes and 30 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between 3fa1311 and 0f1abd6.

Walkthrough

In version 0.4.20 of the yorkie-js-sdk, several enhancements and optimizations were introduced. Key updates include improved XML generation in the Tree.toXML method, enhanced type inference in Document.subscribe, and new implementations like RHT.GC and GCPair for TreeNode and TextNode. Additionally, the push-only sync mode was optimized for better performance. The package version was updated from 0.4.19 to 0.4.20.

Changes

File Change Summary
CHANGELOG.md Documented new features, enhancements, and optimizations in version 0.4.20.
package.json Updated version number from 0.4.19 to 0.4.20.
Various Classes Improved Tree.toXML for valid XML, enhanced Document.subscribe type inference, introduced RHT.GC, optimized push-only sync mode, and implemented GCPair for TreeNode and TextNode.

🌸✨
In the realm of code, where changes weave,
New features bloom, and bugs take leave.
With 0.4.20, our syncs now fly,
Trees speak XML, reaching for the sky.
Subscribe with ease, types inferred,
In Yorkie's forest, progress is stirred.
🌿🐇


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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 May 24, 2024 07:22
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: 1

Outside diff range and nitpick comments (3)
CHANGELOG.md (3)

Line range hint 164-164: Correct the missing apostrophe in the entry about the 'simultaneous-cursors' example.

- Add README and thumbnail on example 'simultaneous-cursors'by @banma1234 in https://github.com/yorkie-team/yorkie-js-sdk/pull/819
+ Add README and thumbnail on example 'simultaneous-cursors' by @banma1234 in https://github.com/yorkie-team/yorkie-js-sdk/pull/819

Line range hint 106-106: Capitalize "Chrome" in the entry about the devtools chrome extension.

- Implement devtools chrome extension by @chacha912 in https://github.com/yorkie-team/yorkie-js-sdk/pull/717
+ Implement devtools Chrome extension by @chacha912 in https://github.com/yorkie-team/yorkie-js-sdk/pull/717

Line range hint 98-98: Add a hyphen to "Follow up" to form the compound adjective "Follow-up".

- Follow up work after devtools mvp by @chacha912 in https://github.com/yorkie-team/yorkie-js-sdk/pull/734
+ Follow-up work after devtools mvp by @chacha912 in https://github.com/yorkie-team/yorkie-js-sdk/pull/734
Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between a3990d5 and 3fa1311.
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Additional Context Used
LanguageTool (4)
CHANGELOG.md (4)

Near line 98: ‘Follow up’ seems to be a compound adjective before a noun. Use a hyphen: “Follow-up”.
Context: ...am/yorkie-js-sdk/pull/735 ### Fixed - Follow up work after devtools mvp by @chacha912 i...


Near line 106: The proper noun “Chrome” (= software from Google) needs to be capitalized.
Context: ...-01-19 ### Added - Implement devtools chrome extension by @chacha912 in https://gith...


Near line 164: Unpaired symbol: ‘'’ seems to be missing
Context: ...1 - Add README and thumbnail on example 'simultaneous-cursors'by @banma1234 in ht...


Near line 726: There seems to be a noun/verb agreement error. Did you mean “collects” or “collected”?
Context: ... - 2021-01-01 ### Added - Add garbage collect for Container type: #101 ### Changed ...

Markdownlint (165)
CHANGELOG.md (165)

12: null
Bare URL used


13: null
Bare URL used


14: null
Bare URL used


15: null
Bare URL used


16: null
Bare URL used


17: null
Bare URL used


23: null
Bare URL used


27: null
Bare URL used


28: null
Bare URL used


29: null
Bare URL used


30: null
Bare URL used


31: null
Bare URL used


32: null
Bare URL used


33: null
Bare URL used


37: null
Bare URL used


38: null
Bare URL used


39: null
Bare URL used


40: null
Bare URL used


41: null
Bare URL used


42: null
Bare URL used


43: null
Bare URL used


49: null
Bare URL used


55: null
Bare URL used


59: null
Bare URL used


60: null
Bare URL used


61: null
Bare URL used


62: null
Bare URL used


63: null
Bare URL used


69: null
Bare URL used


75: null
Bare URL used


79: null
Bare URL used


83: null
Bare URL used


84: null
Bare URL used


85: null
Bare URL used


86: null
Bare URL used


87: null
Bare URL used


93: null
Bare URL used


94: null
Bare URL used


98: null
Bare URL used


99: null
Bare URL used


100: null
Bare URL used


106: null
Bare URL used


110: null
Bare URL used


111: null
Bare URL used


112: null
Bare URL used


113: null
Bare URL used


117: null
Bare URL used


118: null
Bare URL used


124: null
Bare URL used


128: null
Bare URL used


129: null
Bare URL used


130: null
Bare URL used


131: null
Bare URL used


137: null
Bare URL used


138: null
Bare URL used


139: null
Bare URL used


143: null
Bare URL used


149: null
Bare URL used


150: null
Bare URL used


151: null
Bare URL used


155: null
Bare URL used


156: null
Bare URL used


157: null
Bare URL used


163: null
Bare URL used


164: null
Bare URL used


165: null
Bare URL used


169: null
Bare URL used


170: null
Bare URL used


174: null
Bare URL used


175: null
Bare URL used


181: null
Bare URL used


182: null
Bare URL used


183: null
Bare URL used


184: null
Bare URL used


185: null
Bare URL used


186: null
Bare URL used


187: null
Bare URL used


191: null
Bare URL used


195: null
Bare URL used


196: null
Bare URL used


197: null
Bare URL used


198: null
Bare URL used


204: null
Bare URL used


205: null
Bare URL used


206: null
Bare URL used


207: null
Bare URL used


208: null
Bare URL used


209: null
Bare URL used


210: null
Bare URL used


214: null
Bare URL used


215: null
Bare URL used


216: null
Bare URL used


217: null
Bare URL used


221: null
Bare URL used


222: null
Bare URL used


226: null
Bare URL used


227: null
Bare URL used


228: null
Bare URL used


234: null
Bare URL used


235: null
Bare URL used


236: null
Bare URL used


237: null
Bare URL used


238: null
Bare URL used


239: null
Bare URL used


240: null
Bare URL used


244: null
Bare URL used


245: null
Bare URL used


246: null
Bare URL used


247: null
Bare URL used


248: null
Bare URL used


249: null
Bare URL used


250: null
Bare URL used


256: null
Bare URL used


257: null
Bare URL used


258: null
Bare URL used


259: null
Bare URL used


260: null
Bare URL used


261: null
Bare URL used


267: null
Bare URL used


268: null
Bare URL used


272: null
Bare URL used


273: null
Bare URL used


274: null
Bare URL used


275: null
Bare URL used


279: null
Bare URL used


280: null
Bare URL used


284: null
Bare URL used


285: null
Bare URL used


286: null
Bare URL used


292: null
Bare URL used


293: null
Bare URL used


299: null
Bare URL used


303: null
Bare URL used


307: null
Bare URL used


313: null
Bare URL used


314: null
Bare URL used


315: null
Bare URL used


321: null
Bare URL used


322: null
Bare URL used


323: null
Bare URL used


324: null
Bare URL used


330: null
Bare URL used


334: null
Bare URL used


335: null
Bare URL used


341: null
Bare URL used


342: null
Bare URL used


346: null
Bare URL used


347: null
Bare URL used


372: null
Bare URL used


373: null
Bare URL used


374: null
Bare URL used


378: null
Bare URL used


379: null
Bare URL used


387: null
Bare URL used


393: null
Bare URL used


397: null
Bare URL used


398: null
Bare URL used


399: null
Bare URL used


400: null
Bare URL used


404: null
Bare URL used


410: null
Bare URL used


411: null
Bare URL used


412: null
Bare URL used


413: null
Bare URL used


417: null
Bare URL used

Additional comments not posted (1)
CHANGELOG.md (1)

10-18: Ensure all entries under version 0.4.20 accurately reflect the changes made in the corresponding pull requests.

Verification successful

The entries in the CHANGELOG.md for version 0.4.20 have been verified against the corresponding pull requests, and they accurately reflect the changes made. Here are the details:

No discrepancies were found between the CHANGELOG entries and the pull request details.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the accuracy of the entries in CHANGELOG.md for version 0.4.20 by checking the corresponding pull requests.

# Check the pull requests mentioned in the entries for version 0.4.20
cat CHANGELOG.md | grep -A 8 "## \[0.4.20\]" | grep -oP 'https://github.com/yorkie-team/yorkie-js-sdk/pull/\d+' | xargs -n 1 curl -s | jq '.title, .body'

Length of output: 155



Script:

#!/bin/bash
# Description: Verify the accuracy of the entries in CHANGELOG.md for version 0.4.20 by checking the corresponding pull requests.

# Extract the URLs of the pull requests mentioned in the entries for version 0.4.20
urls=$(cat CHANGELOG.md | grep -A 8 "## \[0.4.20\]" | grep -oP 'https://github.com/yorkie-team/yorkie-js-sdk/pull/\d+')

# Fetch the details of these pull requests and output the title and body for verification
for url in $urls; do
  echo "Fetching details for $url"
  curl -s $url | jq '.title, .body'
done

Length of output: 2000



Script:

#!/bin/bash
# Description: Verify the accuracy of the entries in CHANGELOG.md for version 0.4.20 by checking the corresponding pull requests using the GitHub API.

# Extract the pull request numbers from the URLs mentioned in the entries for version 0.4.20
pr_numbers=$(cat CHANGELOG.md | grep -A 8 "## \[0.4.20\]" | grep -oP 'https://github.com/yorkie-team/yorkie-js-sdk/pull/\d+' | grep -oP '\d+')

# Fetch the details of these pull requests using the GitHub API and output the title and body for verification
for pr_number in $pr_numbers; do
  echo "Fetching details for pull request #$pr_number"
  curl -s "https://api.github.com/repos/yorkie-team/yorkie-js-sdk/pulls/$pr_number" | jq '.title, .body'
done

Length of output: 5906

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link

codecov bot commented May 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.41%. Comparing base (a3990d5) to head (3fa1311).

Current head 3fa1311 differs from pull request most recent head 0f1abd6

Please upload reports for the commit 0f1abd6 to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #820      +/-   ##
==========================================
- Coverage   80.48%   80.41%   -0.07%     
==========================================
  Files          59       59              
  Lines        4535     4535              
  Branches      918      918              
==========================================
- Hits         3650     3647       -3     
- Misses        617      620       +3     
  Partials      268      268              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

CHANGELOG.md Outdated Show resolved Hide resolved
@hackerwins hackerwins merged commit fea1a0e into main May 24, 2024
2 checks passed
@hackerwins hackerwins deleted the v0.4.20 branch May 24, 2024 07:28
hackerwins added a commit that referenced this pull request May 24, 2024
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