Skip to content

Conversation

@juliusmarminge
Copy link
Member

@juliusmarminge juliusmarminge commented Sep 16, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced request body handling by allowing only specific HTTP methods (POST, PUT, PATCH) to include request bodies.
    • Added comprehensive tests for router configuration across multiple adapter modules to ensure consistent response for GET requests.
  • Bug Fixes

    • Improved robustness of the request body processing by bypassing parsing for unsupported methods.

@vercel
Copy link

vercel bot commented Sep 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-uploadthing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 16, 2024 6:25pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
legacy-docs-uploadthing ⬜️ Ignored (Inspect) Visit Preview Sep 16, 2024 6:25pm

@changeset-bot
Copy link

changeset-bot bot commented Sep 16, 2024

⚠️ No Changeset found

Latest commit: 1a8cb26

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 16, 2024

Walkthrough

The changes introduce a new helper function, isBodyAllowed, to determine which HTTP methods ("POST", "PUT", and "PATCH") can have a request body. The getPostBody function is updated to utilize this helper, allowing it to return undefined for disallowed methods, with an adjusted return type. Additionally, tests are added to verify that the router configuration is correctly returned for GET requests across various adapter modules, enhancing test coverage.

Changes

File Path Change Summary
packages/uploadthing/src/internal/to-web-request.ts Added isBodyAllowed function; modified getPostBody to return undefined for disallowed methods; updated return type to allow undefined.
packages/uploadthing/test/adapters.test.ts Added tests for GET requests across multiple adapters to verify router configuration and response structure.

Poem

In the meadow where bunnies play,
A new rule has brightened the day.
With methods now checked,
No body to wreck,
Our code hops along, come what may! 🐇✨


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 149ff63 and 1a8cb26.

Files selected for processing (1)
  • packages/uploadthing/src/internal/to-web-request.ts (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • packages/uploadthing/src/internal/to-web-request.ts

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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai generate interesting stats about this repository and render them as a table.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Sep 16, 2024

@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2024

📦 Bundle size comparison

Bundle Size (gzip) Visualization
Main 26.03KB See Treemap 📊
PR (5eae957) 26.03KB See Treemap 📊
Diff No change

Copy link
Collaborator

@markflorkowski markflorkowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL body on GET is not actually spec-forbidden, but it just has no semantic meaning in the spec, and is generally "not recommended"

@juliusmarminge
Copy link
Member Author

TIL body on GET is not actually spec-forbidden, but it just has no semantic meaning in the spec, and is generally "not recommended"

CleanShot 2024-09-16 at 19 24 32

@markflorkowski
Copy link
Collaborator

TIL body on GET is not actually spec-forbidden, but it just has no semantic meaning in the spec, and is generally "not recommended"

CleanShot 2024-09-16 at 19 24 32

image

@juliusmarminge
Copy link
Member Author

juliusmarminge commented Sep 16, 2024

Interesting... then Node aint spec compliant, nor is Chrome

CleanShot 2024-09-16 at 19 28 51

@markflorkowski
Copy link
Collaborator

Interesting... then Node aint spec compliant, nor is Chrome

I think since the spec doesn't specify behaviour, they can implement it how they want, and everyone has just agreed that GET doesn't have a body, even if the spec is wishy-washy on it hahah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants