[EDU-1590] Update JS API references to match ably-js v2.9 API

[VeskeR]

Description

Based on the work done by @m-hulbert in 521c24f, this PR adds final changes in de8f17d to update all JS API docs to match latest ably-js v2.9 release.

Note:

• This PR does not add the annotations API: Message.summary, Annotation message, RestAnnotations and RealtimeAnnotations are not included in this PR. Should be added once Feature/pub 1676 message annotations #2642 is completed and merged.
• This PR does not update the LiveObjects API references at https://ably.com/docs/liveobjects. For now it will still point to the TypeDoc, until API is no longer experimental

Resolves EDU-1590

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

[VeskeR]

@m-hulbert There are couple of rendering issues I wasn't able to resolve, would like to get your help with them:

1. content\partials\rest\_request.textile - has those big separator lines in its parameters. Probably becuase I've used blang inside the parameters list (ably-js v2 requires version as a 3rd parameter).
2. content\partials\types\_local_device.textile - shows {{LANG_BLOCK[default]}} when js is selected (and shows javascript or something when other languages are selected). Also Properties header is overlapping the parameters table lines.
3. content\partials\types\_push_channel.textile - always shows <div lang="javascript,nodejs,java,android,swift,objc">

Sreenshots at the bottom.

I think all of those issues are caused by the use of language tags, blang, div and span (with lang attribute), but I have no idea how they should be changed to work properly.

request:

LocalDevice:

PushChannel:

[m-hulbert]

Thanks for finishing this off @VeskeR

I pushed a fixup which sorts out the rendering issues you found. I've also been through everything else and it all seems to be showing the correct info.

Anything that is slightly awry is down to the current toolchain and format, which will be resolved in the not-too-distant-future. The more important thing is to get the updated info out.

[m-hulbert]

Suggested change

	Enter a presence channel with an optional data that is associated with the current present member. If the channel is @initialized@ (i.e. no attempt to attach has yet been made for this channel), then calling @enter@ will implicitly attach the channel.
	Enter a presence channel with optional data that is associated with the current presence member. If the channel is @initialized@ (i.e. no attempt to attach has yet been made for this channel), then calling @enter@ will implicitly attach the channel.

[VeskeR]

I've removed "an", but I think we should leave the "present member" phrasing, as it is what currently used throughout the whole realtime-sdk/presence.textile file, 21 occurrences

[m-hulbert]

Is this correct for device details and local device to be underneath this blang? I think they exist in more SDKs than just Ruby, Flutter and JS.

[ttypic]

I believe they exists in dotnet, java, obj-c, swift as well, but if they haven't been added in API references before, I would suggest adding them in the separate PR (it's a bit out of scope here)

[VeskeR]

I agree with @ttypic here. I've used the existing blang and I don't think we should add changes related to other languages to this PR, as it's quite huge as it is.
It would also require a minimal research to figure out if DeviceDetails and LocalDevice are publicly exposed in other languages, and if so, what fields they have.
I'd prefer we create a separate ticket for this

[ttypic]

All looks good, thanks @VeskeR for adding all this, I spotted couple of places where we have java-style type definitions instead of js/ts

[VeskeR]

@m-hulbert Hey, thanks for going through the updates and helping with rendering issues.

I've noticed that at least locally I can still see LANG_BLOCK bit for the LocalDevice:

Is this one of the things that is hard to fix due to the toolchain/format and you're okay to merge it as is? I don't think I've seen it happen for other partials, so there must be something wrong with my changes I assume.

[ttypic]

LGTM