Fix rate limit name "api-count" → "apiCount" #645
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
This is more consistent, as most options are kebab-case, rather than camelCase. Make both work though, no reason to reject apicount or APICount.
|
Thanks! I added a commit to the PR to fix it so that both work: no reason to reject either |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Setting rate limit for "apiCount" from the command line doesn't seem to work.
"apiCount" is invalid as far as the "-ratelimit" flag is concerned.
But "api-count" is then not a rate limit that is defined in handlers/handlers.go:
goatcounter/handlers/handlers.go
Lines 40 to 41 in a54ca4f