-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace GitHub rate limit functionality with HTTP API rate limit functionality #315
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code analysis identified issues
VIP Code Analysis Bot has identified potential problems in this pull request during automated scanning. We recommend reviewing the issues noted and that they are resolved.
phpcs scanning turned up:
🚫 1 error
This bot provides automated PHP linting and PHPCS scanning. For more information about the bot and available customizations, see our documentation.
Scan run detail
Software versions
Options file (
|
PHP lint optionsPHP lint files enabled:
Lint modified files only:
Directories not PHP linted:
SVG configurationSVG scanning enabled:
Auto-approval configurationAuto-approvals enabled:
Non-functional changes auto-approved:
Auto-approved file-types:
|
PHPCS configurationPHPCS scanning enabled:
PHPCS severity level:
Standard(s) used:
Runtime set:
Custom sniffs included:
Custom sniffs excluded:
Directories not PHPCS scanned:
WPScan API configurationWPScan API scanning enabled:
|
Dismissing review as all inline comments are obsolete by now
No issues were found to report when scanning latest commit (commit-ID: 175a8c3) This bot provides automated PHP linting and PHPCS scanning. For more information about the bot and available customizations, see our documentation. Scan run detail
|
This pull request replaces the previous GitHub rate limit functionality with generic HTTP API rate limit functionality. This means that the functionality can cover other types of HTTP APIs. Furthermore, this new functionality is passive, meaning it does not make HTTP requests (saving resources), but rather records incoming HTTP response headers and keeps a record internally.
TODO:
vipgoci_http_api_rate_limit_usage()
):vipgoci_github_rate_limit_usage()
).vipgoci_http_api_rate_limits_check()
tovipgoci_http_api_rate_limit_check()
for consistency.vipgoci_http_api_rate_limit_usage()
in main.phptests/integration/GitHubRateLimitUsageTest.php
.tests/unit/HttpApiRateLimitUsageTest.php
for new function.tests/unit/HttpFunctionsHttpApiRateLimitsCheckTest.php
.PHPDoc
comments are up to date for functions added or alteredvip-go-compatibility-scanner
[ Replace GitHub rate limit function with HTTP API rate limit function vip-go-compatibility-scanner#46 ]