You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have an integration test failure in Swift (ably/ably-chat-swift#169) because chat messages are missing a latestAction key. It looks like the field names that were introduced into this spec in #216 no longer match those being used by Realtime. The JS Chat SDK was updated to use the new field names in ably/ably-chat-js#427 but this hasn't been reflected in the spec.
From what I can tell from that JS PR:
latestAction is now action
latestActionSerial is now version
latestActionDetails is now operation
Please can the spec be updated so that we can update Swift accordingly?
The text was updated successfully, but these errors were encountered:
Upon our integration tests starting to fail, we noticed that Realtime
seems to have renamed the `latestAction` property to `action`. This
change has not yet been reflected in the spec, but has been in JS [1].
I’ve created an issue to get the spec updated [2] but since this test
failure is stopping us from merging anything else I am going to rename
this property until we get a more definitive answer.
Part of #169.
[1] ably/ably-chat-js#427
[2] ably/specification#254
We currently have an integration test failure in Swift (ably/ably-chat-swift#169) because chat messages are missing a
latestAction
key. It looks like the field names that were introduced into this spec in #216 no longer match those being used by Realtime. The JS Chat SDK was updated to use the new field names in ably/ably-chat-js#427 but this hasn't been reflected in the spec.From what I can tell from that JS PR:
latestAction
is nowaction
latestActionSerial
is nowversion
latestActionDetails
is nowoperation
Please can the spec be updated so that we can update Swift accordingly?
The text was updated successfully, but these errors were encountered: