ljharb/qs

Add the ability to enable strict RFC 3986 conformance for decoding as well as encoding

Open

#205 创建于 2017年4月10日

在 GitHub 查看
 (1 评论) (5 反应) (0 负责人)JavaScript (8,015 star) (744 fork)batch import
enhancementhelp wantedparsesemver-minor: new features

描述

To achieve strict RFC 3986 conformance (specifically, '+' in query strings is a LITERAL '+' and not a placeholder for ' ' as per the W3C's URL recommendations, the following is necessary:

qs.parse(s, {
    decoder: (str) => {
        try {
            return decodeURIComponent(str);
        } catch (e) {
            return str;
        }
    },
})

For those of us who prefer strict RFC 3986 conformance, I suggest an option like:

qs.parse(s, {
    format: 'RFC3986',
})

which would be much more concise and not require knowing the implementation details of the default decode function.

贡献者指南

技术栈
javascriptnodejs
领域
apibackend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
understanding of RFC 3986basic JavaScriptfamiliarity with qs library
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
55
研究方向
To implement this feature, examine the current decode function in lib/parse.js and add a 'format' option that, when set to 'RFC3986', uses decodeURIComponent for decoding. Ensure that the default behavior (legacy mode) remains unchanged. Consider adding tests in test/parse.js to verify conformance. The issue suggests a concise API, so the solution should be localized to the parse function and its options.