-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
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
Create tree-shakeable Msgpack
module
#1375
Comments
➤ Automation for Jira commented: The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3718 |
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
This is preparation for #1375 (making MessagePack functionality tree-shakable), in which there may not be a MessagePack implementation available. We update normaliseClientOptions so that it only sets useBinaryProtocol to true if there is a MessagePack implementation available.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
This is preparation for #1375 (making MessagePack functionality tree-shakable), in which there may not be a MessagePack implementation available. We update normaliseClientOptions so that it only sets useBinaryProtocol to true if there is a MessagePack implementation available.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 21, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
This is preparation for #1375 (making MessagePack functionality tree-shakable), in which there may not be a MessagePack implementation available. We update normaliseClientOptions so that it only sets useBinaryProtocol to true if there is a MessagePack implementation available.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
This is preparation for #1375 (making MessagePack functionality tree-shakable), in which there may not be a MessagePack implementation available. We update normaliseClientOptions so that it only sets useBinaryProtocol to true if there is a MessagePack implementation available.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 22, 2023
lawrence-forooghian
added a commit
that referenced
this issue
Aug 23, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 23, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 23, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 23, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Aug 23, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Sep 5, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Sep 5, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Sep 5, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Sep 5, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Sep 14, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Sep 14, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Sep 14, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Sep 14, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Oct 26, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Nov 7, 2023
Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Nov 7, 2023
The _MsgPack assignment becomes the only place that Platform.Config.msgpack gets accessed. All other uses now instead access _MsgPack. Preparation for #1375 (making MessagePack functionality tree-shakable).
lawrence-forooghian
added a commit
that referenced
this issue
Nov 7, 2023
We move the MessagePack functionality into a tree-shakable MsgPack module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Nov 7, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
lawrence-forooghian
added a commit
that referenced
this issue
Nov 14, 2023
We move it into a tree-shakable RealtimePresence module. Resolves #1375.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BaseClient
andRest
modules #1374Msgpack
which can be passed to theBaseClient
constructorMsgpack
module is not supplied,BaseClient
will use json encoding for all requests and themsgpack
dependency will not be importedThe text was updated successfully, but these errors were encountered: