Merge integration/liveobjects into main

[VeskeR]

Description

Merge integration/liveobjects into main branch to release LiveObjects docs.
All changes were reviewed in the following PRs:

• Add LiveObjects product to site navigation #2464
• Live objects: Add REST API docs #2490
• Add LiveObjects section to platform/index #2525
• Add comment explaining reusing the assetTracking badge color for liveObjects in ExamplesGrid #2526
• [PUB-773] LiveObjects product docs #2463
• [PUB-1588] Add Advanced section for some of the LiveObjects navigation items #2522
• [EDU-1882] - Migrate live objects rest api to open api #2513
• [PUB-1589] Add LiveObjects image for docs homepage #2547
• Remove references to example app from LiveObjects docs #2548
• Update language data for JavaScript SDK to 2.8 for LiveObjects branch #2550
• Feature/pub 1614 live objects rest api #2561
• liveobjects: add inband objects docs #2563
• Merge main into integration/liveobjects 2025-05-08 #2581
• [EDU-1936] Add the experimental flag to LiveObjects #2582
• Update ably-js language version to 2.9 - LiveObjects release #2584

Checklist

• Commits have been rebased.
• Linting has been run against the changed file(s).
• The PR adheres to the writing style guide and contribution guide.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[m-hulbert]

This LGTM 👍

A few things to track going forwards;

• Can we make sure we have an issue to rename 'inband objects' to drop the usage of 'inband' post-release.
• I think we should consolidate info between the REST API usage and the REST API reference.

[mschristensen]

This LGTM 👍

A few things to track going forwards;

• Can we make sure we have an issue to rename 'inband objects' to drop the usage of 'inband' post-release.
• I think we should consolidate info between the REST API usage and the REST API reference.

Created tickets:

• https://ably.atlassian.net/browse/PUB-1685
• https://ably.atlassian.net/browse/PUB-1686