feat(http): configure standard shield - #131
Conversation
Expose standard-stage and handler options while preserving default ordering and shared state semantics.\n\nRefs #126
|
Warning Review limit reached
Next review available in: 18 minutes Limit details: You’ve used all 10 included reviews currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
Comment |
Summary
StandardHttpShieldOptionsfor every standard pipeline stageAddStandardShieldcallbacksBenchmark
The 1.5% mean difference is within overlapping confidence intervals; allocation is unchanged.
Test plan
dotnet build Kevlar.slnx -c Releasedotnet run --project tests/Kevlar.Tests -c Release --no-build -- --timeout 5m(678 passed)dotnet run --project tests/Kevlar.IntegrationTests -c Release --no-build -- --timeout 5m(108 passed)dotnet run --project tests/Kevlar.NetStandard.Tests -c Release --no-build -- --timeout 5m(5 passed)npm run build --prefix docspwsh scripts/Verify-DocSnippets.ps1 -PackagesPath artifacts/package/release -Version 0.0.0-issue126pwsh scripts/Verify-Packages.ps1 -PackagesPath artifacts/package/release -Version 0.0.0-localCloses #126