Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitb93c894

Browse files
authored
[backport] fix: update the config.api.responseLimit type (#82852) (#83028)
`config.api.responseLimit` can also be [set to`false`](#82842 (comment)).Because of the limitations of type inference on JS files, we need to setthe type to `boolean`.See#82842 (comment)<!-- Thanks for opening a PR! Your contribution is much appreciated.To make sure your PR is handled as smoothly as possible we request thatyou follow the checklist sections below.Choose the right checklist for the change(s) that you're making:## For Contributors### Improving Documentation- Run `pnpm prettier-fix` to fix formatting issues before opening thePR.- Read the Docs Contribution Guide to ensure your contribution followsthe docs guidelines:https://nextjs.org/docs/community/contribution-guide### Adding or Updating Examples- The "examples guidelines" are followed from our contributing dochttps://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md- Make sure the linting passes by running `pnpm build && pnpm lint`. Seehttps://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md### Fixing a bug- Related issues linked using `fixes #number`- Tests added. See:https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md### Adding a feature- Implements an existing feature request or RFC. Make sure the featurerequest has been accepted for implementation before opening a PR. (Adiscussion must be opened, seehttps://github.com/vercel/next.js/discussions/new?category=ideas)- Related issues/discussions are linked using `fixes #number`- e2e tests added(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)- Documentation added- Telemetry added. In case of a feature if it's used or not.- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md## For Maintainers- Minimal description (aim for explaining to someone not on the team tounderstand the PR)- When linking to a Slack thread, you might want to share details of theconclusion- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues- Add review comments if necessary to explain to the reviewer the logicbehind a change### What?### Why?### How?Closes NEXT-Fixes #-->
1 parent8a92f28 commitb93c894

File tree

1 file changed

+1
-1
lines changed
  • packages/next/src/server/lib/router-utils

1 file changed

+1
-1
lines changed

‎packages/next/src/server/lib/router-utils/typegen.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -567,7 +567,7 @@ export function generateValidatorFile(
567567
config?: {
568568
api?: {
569569
bodyParser?: boolean | { sizeLimit?: string }
570-
responseLimit?: string | number
570+
responseLimit?: string | number | boolean
571571
externalResolver?: boolean
572572
}
573573
runtime?: 'edge' | 'experimental-edge' | 'nodejs' | string // necessary unless config is exported as const

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp