chore: fix typographical errors and improve consistency in features.md#438
Merged
chore: fix typographical errors and improve consistency in features.md#438
features.md#438Conversation
VeskeR
reviewed
Mar 11, 2026
specifications/features.md
Outdated
| - `(RSL1h)` The `publish(name, data)` form should not take any additional arguments. If a client library has supported additional arguments to the `(name, data)` form (e.g. separate arguments for `clientId` and `extras`, or a single `attributes` argument) in any 1.x version, it should continue to do so until version 2.0. | ||
| - `(RSL1i)` If the total size of the message or (if publishing an array) messages, calculated per [TO3l8](#TO3l8), exceeds the `maxMessageSize`, then the client library should reject the publish and indicate an error with code 40009 | ||
| - `(RSL1j)` When `Message` objects are provided, any valid `Message` attribute (that is, an attribute specified in [TM2](#TM2)) that is supplied by the caller must be included in the encoded message. (This does not mean it must be included *unaltered*; for example the `data` and `encoding` will be subject to processing per [RSL4](#RSL4)) | ||
| - `(RSL1j)` When `Message` objects are provided, any valid `Message` attribute (that is, an attribute specified in [TM2](#TM2)) that is supplied by the caller must be included in the encoded message, with the exception of the `annotations` field (`TM2u`) which must never be serialized when sending a message to Ably. (This does not mean other attributes must be included *unaltered*; for example the `data` and `encoding` will be subject to processing per [RSL4](#RSL4)) |
Contributor
There was a problem hiding this comment.
with the exception of the
annotationsfield (TM2u) which must never be serialized when sending a message to Ably
where did this come from?
Contributor
Author
There was a problem hiding this comment.
oh, sorry, it's true, but it was unstashed changes, I'll revert
- Corrected formatting issues (`annotations`, `'@'` characters, etc.). - Improved consistency in spec point references and removed redundant/unnecessary characters.
ttypic
force-pushed
the
fix-markdown-issues
branch
from
81d514f to
53892e5
Compare
VeskeR
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
annotations,'@'characters, etc.).