This repository has been archived by the owner on May 26, 2022. It is now read-only.
更新 json unmarshal 型態黑名單 #9
Merged
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
由於蝦皮在取得訂單詳細資訊時，在 `buyer_cancel_reason`、`cancel_reason` 時常會出現 0 值，使程式讀取出來 `json.Unmarshal` 會出現這樣的錯誤: ``` ReadString: expects " or n, but found 0, error found in teacat#10 byte of ...|reason": 0, "recipie|..., bigger context ...| ``` 注意於 `reason": 0` 處， reason 原應為字串，但有時系統會回傳數值。 因此對本列表進行更新。
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
由於蝦皮在取得訂單詳細資訊時，在
buyer_cancel_reason、cancel_reason時常會出現 0 值，使程式讀取出來json.Unmarshal會出現這樣的錯誤:注意於
reason": 0處， reason 原應為字串，但有時系統會回傳數值。因此對本列表進行更新。