Device details refactoring #1441
Draft
Conversation
This file contains 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
…t `ARTDevicePushStatus`. Parse response as `ARTDeviceDetailsResponse` instead of `ARTDevicePushDetails`.
maratal
requested review from
QuintinWillison and
lawrence-forooghian
and removed request for
QuintinWillison
…`ARTDeviceDetailsResponse`.
|
Thanks for opening this, @maratal. I've replied here: ably/specification#25 – let’s keep the conversation going there? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a preview of a possible solution for ably/specification#25
Since it's a part of a discussion I'll keep it in draft state.
The idea:
ARTDeviceDetailsdoesn't contain always empty pushstateanderrorReasonfields anymore. But you still get these values in thepush/admin/deviceRegistrations/get:function as a part ofARTDeviceDetailsResponseobject.