Add multi_value_param_names option and rewrite README#9
Merged
Conversation
Adds a new optional setting `multi_value_param_names` to `query_string_parser` that emits only the listed parameter names as arrays, leaving the rest as scalars. This is more ergonomic than the all-or-nothing `multi_value_params true` when only a few keys are known to repeat. `multi_value_params` takes precedence when both are set so existing behavior is preserved. The README is also rewritten with input → output examples for each option, an overview of what the plugins do, and a single options table. Closes #7 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #7
Summary
multi_value_param_namestoquery_string_parserso users can promote only listed parameters to arrays, instead of forcing every parameter into an array viamulti_value_params truemulti_value_params truekeeps precedence when both are set, so existing configurations are unaffectedBehavior
tag=ruby&tag=fluentd&lang=ja{ "tag": "fluentd", "lang": "ja" }(last wins)multi_value_params true{ "tag": ["ruby", "fluentd"], "lang": ["ja"] }multi_value_param_names tag{ "tag": ["ruby", "fluentd"], "lang": "ja" }Test plan
bundle exec rake test(20 tests / 87 assertions / 0 failures)multi_value_paramsprecedence overmulti_value_param_names🤖 Generated with Claude Code