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 LiveObjects product to site navigation #2464

Open
wants to merge 1 commit into
base: PUB-773/liveobjects-product-docs
Choose a base branch
from

Conversation

VeskeR
Copy link
Contributor

@VeskeR VeskeR commented Mar 5, 2025

Description

Adds navigation for LiveObjects product in src folder.

This was added by searching for "livesync" in "src" folder and adding corresponding "liveObjects" sections where necessary.

Currently missing:

Checklist

@VeskeR VeskeR requested a review from a team March 5, 2025 09:20
Copy link

coderabbitai bot commented Mar 5, 2025

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
🪧 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 generate docstrings to generate docstrings for 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.

@ably-ci ably-ci temporarily deployed to ably-docs-liveobjects-n-jiwpew March 5, 2025 09:20 Inactive
@VeskeR VeskeR mentioned this pull request Mar 5, 2025
11 tasks
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from 9ac84e8 to e5e6ece Compare March 5, 2025 09:26
@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 3bfe8d2 to 145457e Compare March 5, 2025 09:31
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from e5e6ece to 48b36e8 Compare March 5, 2025 09:41
@m-hulbert m-hulbert temporarily deployed to ably-docs-liveobjects-n-jiwpew March 5, 2025 09:50 Inactive
@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 145457e to 5d95e7f Compare March 6, 2025 09:15
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from 48b36e8 to c284b79 Compare March 6, 2025 09:16
@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 5d95e7f to 1f7289e Compare March 7, 2025 09:10
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from c284b79 to 4c70358 Compare March 7, 2025 09:16
@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 1f7289e to 2f870cd Compare March 7, 2025 09:18
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from 4c70358 to 8b99a80 Compare March 7, 2025 09:18
title: 'LiveObjects',
type: 'feature',
content: 'Seamlessly sync application state between clients.',
image: 'liveobjects.png',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this needs to be added

@@ -31,6 +31,9 @@ export default {
javascript: 0.4,
react: 0.4,
},
liveObjects: {
javascript: 2.6,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

not sure about this one. LiveObjects is not a separate product, so it doesn't have its own versioning.
will it inherit the pub/sub SDKs version then? e.g. 2.6 for ably-js

cc @mschristensen

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes I think we should just specify the Ably JS version

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok, works for me.

Also, technically, it wouldn't be 2.6, as with the liveobjects release we will bump the minor version in ably-js to at least 2.7 (or more if other versions released before that).

@ably/team-deved would you guys prefer:

  1. this PR to have 2.6 version in this PR, and then open a second PR to update the ably-js versions for all products (not just liveobjects) to higher version once it's published
  2. keep this PR open until ably-js is published and change the version here to the actual one, as well as for other products?

Copy link
Contributor

Choose a reason for hiding this comment

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

Assuming that LiveObjects is the only change going into 2.7 of ably-js then I think we can just bump both of them to 2.7 in this PR.

Copy link
Contributor Author

@VeskeR VeskeR Mar 19, 2025

Choose a reason for hiding this comment

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

sgtm, I've preemptively updated it to 2.7 for everything, but will change it again if we end up releasing liveobjects under another minor ably-js version

@VeskeR VeskeR marked this pull request as ready for review March 7, 2025 09:22
@GregHolmes GregHolmes temporarily deployed to ably-docs-liveobjects-n-jiwpew March 7, 2025 09:35 Inactive
@mschristensen
Copy link
Contributor

Looks good, we just need some assets from the design team - I'll follow up with Jamie

@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch 2 times, most recently from 7c9bad3 to 25b2298 Compare March 11, 2025 08:24
@VeskeR VeskeR force-pushed the liveobjects-navigation branch 2 times, most recently from f674eaa to 28b40a7 Compare March 11, 2025 08:47
@VeskeR
Copy link
Contributor Author

VeskeR commented Mar 11, 2025

I've removed the Setup page as we decided to drop it in favor of Quickstart: #2463 (comment)

@m-hulbert m-hulbert temporarily deployed to ably-docs-liveobjects-n-jiwpew March 12, 2025 08:56 Inactive
@@ -31,6 +31,9 @@ export default {
javascript: 0.4,
react: 0.4,
},
liveObjects: {
javascript: 2.6,
Copy link
Contributor

Choose a reason for hiding this comment

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

Assuming that LiveObjects is the only change going into 2.7 of ably-js then I think we can just bump both of them to 2.7 in this PR.

Comment on lines +41 to +50
name: 'Batch Operations',
link: '/docs/liveobjects/batch',
},
{
name: 'Lifecycle Events',
link: '/docs/liveobjects/lifecycle',
},
{
name: 'Typing',
link: '/docs/liveobjects/typing',
Copy link
Contributor

Choose a reason for hiding this comment

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

As per my review on the main PR; I wonder if the features should remain only LiveCounter and LiveMap, and then these 3 items fall under a separate heading. Any thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

then these 3 items fall under a separate heading. Any thoughts?

Not against putting them under a separate heading. Honestly, they're under LiveObjects features heading right now because I couldn't think of another collective name for these three.
Any ideas?

@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 25b2298 to 453be49 Compare March 18, 2025 09:14
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from 28b40a7 to 266f785 Compare March 18, 2025 09:15
@VeskeR VeskeR force-pushed the PUB-773/liveobjects-product-docs branch from 70e3d74 to 0d1c04b Compare March 18, 2025 09:39
@VeskeR VeskeR force-pushed the liveobjects-navigation branch from 266f785 to 1fc1b12 Compare March 18, 2025 09:39
This was added by searching for "livesync" in "src" folder and adding
corresponding "liveObjects" sections where necessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants