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
@funkyboy this issue, issue ably/docs#389 and ably/docs#390 are all really the same issue, so I would prefer in future we keep very related problems in one issue as clearly all three can be dealt with in one PR / fix.
Additionally, the issue is not that ClientOptions should tell what the default value is, but that some ambiguity in the spec exists because admittedly ".. When true, token authentication will always be used by the client." implies that it's false by default, but not that is not explicit enough.
So please close all three issues and perhaps just do a single PR / issue to address the ambiguities in the spec definitions.
@funkyboy also you omitted tags for all of these issues, please remember to tag issues when you create them.
funkyboy
changed the title
ClientOptions should tell what's the default value for useTokenAuth
More explicit default values for ClientOptions' useTokenAuth, queryTime and fallbackHostsUseDefault
Feb 27, 2018
https://docs.ably.io/client-lib-development-guide/features/#TO3j4
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: