[skip ci] Add script to extract redis key/arg count ranges #616
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.
This uses commands.json from redis's documentation to determine which
category a given redis command falls into.
This will be useful to ensure that twemproxy stays up to date with new redis
commands. (but the new script still requires a lot of manual work).
This was used to generate the previously added documentation and determine which redis commands to add where.
Problem
It's difficult to manually track which redis commands have which key/argument counts for dozens of commands
Solution
Track this in a script which will output information about any missing or out of date redis command argument info.