haskell/aeson

Add saner ByteString instances

Open

#187 创建于 2014年3月5日

在 GitHub 查看
 (22 评论) (3 反应) (0 负责人)Haskell (1,298 star) (334 fork)batch import
blocked by upstream/should be done externallyhelp wantedneeds decision

描述

ByteString instances were removed because they allowed people to try and insert arbitrary binary data that JSON can't handle.

Could we not re-add ByteString instances that leveraged something like base64 encoding (which JSON can take I believe) to work around this limitation?

<mgsloan> Fuuzetsu: Best thing to do is to avoid putting bytestrings in json,
          but when it's unavoidable:
          https://gist.github.com/mgsloan/bfe4bf2250c1d656a2b1  [05:03]

贡献者指南

技术栈
无
领域
backenddata
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
HaskellByteStringJSONbase64
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Examine the linked gist (https://gist.github.com/mgsloan/bfe4bf2250c1d656a2b1) for a previous implementation of ByteString instances using base64. Review the aeson source code, particularly the Data.Aeson.Types and Data.Aeson.Encoding modules, to understand where instances are defined and how existing types handle custom encodings. Check the issue comments for any additional constraints or rejection reasons for the prior removed instances.