[ECO-5188] fix: message actions based on specification update

[ttypic]

Spec Update

Summary by CodeRabbit

• Changes
  • Removed deprecated message action constants
  • Reordered and renumbered MessageAction enum constants
  • Added a new MESSAGE_SUMMARY constant
  • Updated test cases to reflect new message action values

[coderabbitai]

Walkthrough

The pull request modifies the MessageAction enum in the Ably Java library, specifically reordering and removing certain enum constants. Three constants (MESSAGE_UNSET, ANNOTATION_CREATE, and ANNOTATION_DELETE) have been removed, while the remaining constants have been renumbered. A new constant MESSAGE_SUMMARY has been added, and the tryFindByOrdinal method remains unchanged. The corresponding test file MessageTest.java has been updated to reflect these changes, adjusting the expected action values in serialization and deserialization tests.

Changes

File	Change Summary
lib/src/main/java/io/ably/lib/types/MessageAction.java	- Removed constants: MESSAGE_UNSET, ANNOTATION_CREATE, ANNOTATION_DELETE - Renumbered constants: MESSAGE_CREATE (0), MESSAGE_UPDATE (1), MESSAGE_DELETE (2) - Moved META_OCCUPANCY to ordinal 3 - Added new constant MESSAGE_SUMMARY at ordinal 4
lib/src/test/java/io/ably/lib/types/MessageTest.java	- Updated test assertions to reflect new action values - Changed expected action value from 1 to 0 in serialization tests

Assessment against linked issues

Objective	Addressed	Explanation
Update ably-java to reflect message action spec changes [ECO-5188]	✅

Poem

🐰 Hop, hop, through the code we go,
Constants shuffled, ordinals in a row,
MessageAction's dance, a rabbit's delight,
Enum refactored, everything feels right! 🌟

Finishing Touches

• 📝 Generate Docstrings

---

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>, 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2c0f111 and 642f7ef.

📒 Files selected for processing (2)

• lib/src/main/java/io/ably/lib/types/MessageAction.java (1 hunks)
• lib/src/test/java/io/ably/lib/types/MessageTest.java (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: check (29)
• GitHub Check: check-rest-okhttp
• GitHub Check: check-rest
• GitHub Check: check (24)
• GitHub Check: check-realtime
• GitHub Check: check (21)
• GitHub Check: check (19)
• GitHub Check: check-realtime-okhttp

🔇 Additional comments (1)

lib/src/test/java/io/ably/lib/types/MessageTest.java (1)

Line range hint 89-93: Verify Test Assertions

The test correctly verifies MESSAGE_CREATE action, but consider:

1. Adding assertions for all new enum values
2. Testing boundary conditions for tryFindByOrdinal
3. Testing serialization format compliance with the specification

[ttypic]

Duplicate