-
-
Notifications
You must be signed in to change notification settings - Fork 8
Settings tools select renaming and layout overflow fix #744
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,12 @@ | ||
| import { clerkMiddleware } from "@clerk/nextjs/server"; | ||
| import { NextResponse } from "next/server"; | ||
|
|
||
| export default clerkMiddleware(); | ||
| export default function middleware(request: any, event: any) { | ||
| if (process.env.NEXT_PUBLIC_PLAYWRIGHT_TEST === "true") { | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This makes the entire Clerk middleware bypass when NEXT_PUBLIC_PLAYWRIGHT_TEST=true. Because this is a NEXT_PUBLIC_ flag and there is no NODE_ENV guard, a production deployment with the flag set would skip Clerk middleware for every matched route, including API and server-action paths. Please keep the test bypass out of production (for example, use a test-only server-side harness) and preserve Clerk middleware in deployed builds. |
||
| return NextResponse.next(); | ||
| } | ||
| return clerkMiddleware()(request, event); | ||
| } | ||
|
|
||
| export const config = { | ||
| matcher: [ | ||
|
|
||
Large diffs are not rendered by default.
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.
This default only applies when the database has no stored value. fetchData still writes any legacy selectedModel directly into the form, while the schema accepts any non-empty string; after removing the old options, an existing user with e.g. Gemini 3.1 Pro will have no matching Select/Radio item and Save will preserve that disallowed value. Please normalize or migrate legacy values to SkyFi/QCX-Terra and enforce the allowlist in the save action.