[Bit Push] A leading exchange has updated the Spot API documentation on GitHub. The main change this time is that the symbol parameter now supports UTF-8 encoding.
However, interestingly, if you actually check the submission records, you will find that the content of this update is actually the same as the previous Commit, just released through a different channel. It seems that the internal update has been officially announced to the public.
For developers, UTF-8 encoding support means being able to handle trading pair symbols more flexibly, especially when special characters are involved.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
8 Likes
Reward
8
5
Repost
Share
Comment
0/400
MrRightClick
· 10h ago
What is this move called, brother, left hand to right hand? The internal document that is released to the public also needs to have a sense of news.
View OriginalReply0
BrokeBeans
· 10h ago
This operation is really amazing; after a long time, it's just moving their own documents to a different location and pretending it's a new feature release.
View OriginalReply0
MevShadowranger
· 10h ago
Um... is this it? It feels like just rephrasing an old feature.
View OriginalReply0
GateUser-6bc33122
· 10h ago
It's just another update with the same old story; what they've already consumed internally is only now being shown to us.
View OriginalReply0
0xLuckbox
· 10h ago
Uh... it's all old content, this time it's just a promotion for the move?
API documentation update for a certain exchange: Spot symbol supports UTF-8 encoding.
[Bit Push] A leading exchange has updated the Spot API documentation on GitHub. The main change this time is that the symbol parameter now supports UTF-8 encoding.
However, interestingly, if you actually check the submission records, you will find that the content of this update is actually the same as the previous Commit, just released through a different channel. It seems that the internal update has been officially announced to the public.
For developers, UTF-8 encoding support means being able to handle trading pair symbols more flexibly, especially when special characters are involved.