docs(cli): improve push publish and batch-publish reference docs#3356
Conversation
- Clarify --message flag: accepts plain text, JSON data, or full message object - Add example showing full message object format for push publish - Update batch-publish payload description with @filename syntax and message field - Add batch-publish example showing "message" field in channel items Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
sacOO7
merged commit 60eb22b
into
feature/ably-cli-reference-documentation
|
Merged since #3353 wasn't able to merge due to some reason : ( |
2 participants
Summary
Improvements to
ably push publishandably push batch-publishreference documentation, on top of #3307.push publish: Clarify--messageflag — accepts plain text, JSON data, or full message object withname/data/extrasfields. Add--messageto all channel-based examples. Add inlinenotification.jsonfile content example.push batch-publish: Document both./filenameand@filenamefile path syntax. Document the optional"message"field in channel items including JSON object format. Add inlinenotifications.jsonfile content example.🤖 Generated with Claude Code