-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: support trace method request #4
Conversation
WalkthroughThis pull request introduces support for the HTTP TRACE method across the library. The changes involve updating package dependencies, adding a new Changes
Sequence DiagramsequenceDiagram
participant Client
participant SuperTest
participant ExpressApp
Client->>SuperTest: trace('/')
SuperTest->>ExpressApp: TRACE request
ExpressApp-->>SuperTest: Respond with 'trace method'
SuperTest-->>Client: Return response
Poem
Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
commit: |
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.
Actionable comments posted: 1
🧹 Nitpick comments (2)
test/supertest.test.ts (2)
207-217
: Consider adding more test scenarios.While the basic TRACE functionality is tested, consider adding tests for:
- Error responses (4xx, 5xx)
- Headers specific to TRACE method
- Request with body (should be ignored as per HTTP spec)
1093-1096
: Consider adding more agent-specific test scenarios.While the basic agent functionality is tested, consider adding tests for:
- TRACE with custom headers
- TRACE with different content types
- Error handling scenarios
Also applies to: 1126-1130
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
package.json
(1 hunks)src/agent.ts
(1 hunks)src/request.ts
(1 hunks)test/supertest.test.ts
(3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: Node.js / Test (windows-latest, 23)
- GitHub Check: Node.js / Test (windows-latest, 22)
- GitHub Check: Node.js / Test (windows-latest, 20)
- GitHub Check: Node.js / Test (windows-latest, 18.19.0)
- GitHub Check: Node.js / Test (windows-latest, 18)
🔇 Additional comments (2)
src/request.ts (1)
59-61
: LGTM! Implementation follows established patterns.The
trace
method implementation is consistent with other HTTP methods in the class, correctly delegating to_testRequest
with the uppercase method name.src/agent.ts (1)
86-88
: LGTM! Implementation follows established patterns.The
trace
method implementation is consistent with other HTTP methods in the class, correctly delegating to_testRequest
with uppercase method name.
[skip ci] ## [8.2.0](v8.1.1...v8.2.0) (2025-01-17) ### Features * support trace method request ([#4](#4)) ([1e3d92b](1e3d92b))
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Summary by CodeRabbit
New Features
Dependency Updates
@arethetypeswrong/cli
to version^0.17.3
@eggjs/bin
version7
egg-bin
version6