Bump up Yorkie to v0.4.23

[chacha912]

What this PR does / why we need it?

• Bump up Yorkie to v0.4.23
• Fetch examples

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

• Chores
  • Updated yorkie-js-sdk to version 0.4.23 across the project for improved performance and bug fixes.

[coderabbitai]

Walkthrough

The updates primarily focus on incrementing the version of the yorkie-js-sdk library from 0.4.22 to 0.4.23 across various parts of the project. This includes changes in environment variables, example files, and the package.json file to ensure consistency and integration of the latest features, improvements, and bug fixes provided by the new version of the library.

Changes

Files/Paths	Change Summary
.env	Incremented NEXT_PUBLIC_YORKIE_VERSION and NEXT_PUBLIC_YORKIE_JS_VERSION to 0.4.23 and updated NEXT_PUBLIC_JS_SDK_URL accordingly.
examples/.../fileInfo.ts	Updated yorkie-js-sdk version from 0.4.22 to 0.4.23.
package.json	Updated yorkie-js-sdk dependency version from 0.4.22 to 0.4.23.

Poem

In the land of code, a version anew,
Yorkie grows stronger, with fixes in view.
From 0.4.22 to 0.4.23,
Bugs are now squashed, and features set free.
Our project now gleams with updates so bright,
Hopping ahead, everything feels right! 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.
  • @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 as 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.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 08a1fec and e1bdc85.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (8)

• .env (1 hunks)
• examples/profile-stack/fileInfo.ts (1 hunks)
• examples/react-tldraw/fileInfo.ts (1 hunks)
• examples/react-todomvc/fileInfo.ts (1 hunks)
• examples/vanilla-codemirror6/fileInfo.ts (1 hunks)
• examples/vanilla-quill/fileInfo.ts (1 hunks)
• examples/vuejs-kanban/fileInfo.ts (1 hunks)
• package.json (1 hunks)

Files not summarized due to errors (4)

• examples/profile-stack/fileInfo.ts: Error: Message exceeds token limit
• examples/react-tldraw/fileInfo.ts: Error: Message exceeds token limit
• examples/react-todomvc/fileInfo.ts: Error: Message exceeds token limit
• examples/vanilla-quill/fileInfo.ts: Error: Message exceeds token limit

Files skipped from review due to trivial changes (4)

• .env
• examples/vanilla-codemirror6/fileInfo.ts
• examples/vuejs-kanban/fileInfo.ts
• package.json

Additional comments not posted (11)

examples/profile-stack/fileInfo.ts (1)

2-2: Verify if version-related changes are missing in this file.

examples/react-todomvc/fileInfo.ts (1)

2-2: Verify if version-related changes are missing in this file.

examples/react-tldraw/fileInfo.ts (5)

2-2: Initialization of Yorkie client and document appears robust.

---

2-2: Callbacks are well-defined and properly use useCallback for performance optimization.

---

2-2: Return statement correctly exposes all necessary handlers and state.

---

2-2: Ensure the DirectoryInfo import path is correct.

---

2-2: Effect handles client and document lifecycle effectively. Ensure all dependencies are correctly listed in the dependency array.

examples/vanilla-quill/fileInfo.ts (4)

2-2: Initialization of Yorkie client and document in the main function appears robust.

---

2-2: Event handling logic is comprehensive and effectively updates the UI and internal state based on document and network events.

---

2-2: Integration with Quill is correctly implemented, ensuring synchronization between the Yorkie document and the Quill editor.

---

2-2: Ensure the DirectoryInfo import path is correct.

[hackerwins]

Thanks for your contribution.