We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can you confirm if JSON values will default to zero now that we will roll out sparse stat support?
Whilst sparse stats for efficiency between client & server is probably the right option, I am not sure the client libraries should be providing empty objects to stat queries so do prefer either a complete JSON object with zero values for each stat, or a more typed approach like we have done in https://github.com/ably/ably-java/blob/master/src/io/ably/types/Stats.java or ably/ably-ruby@cec0349
The text was updated successfully, but these errors were encountered:
a more typed approach
See: 16c1515
Sorry, something went wrong.
Resolved
Nice, this looks great.
paddybyers
No branches or pull requests
Can you confirm if JSON values will default to zero now that we will roll out sparse stat support?
Whilst sparse stats for efficiency between client & server is probably the right option, I am not sure the client libraries should be providing empty objects to stat queries so do prefer either a complete JSON object with zero values for each stat, or a more typed approach like we have done in https://github.com/ably/ably-java/blob/master/src/io/ably/types/Stats.java or ably/ably-ruby@cec0349
The text was updated successfully, but these errors were encountered: