-
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
No ref/phase 3 endpoints #258
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I think the endpoints should be grouped as app/api/schema/...
. Makes it easier to differentiate whether it's an endpoint for the app to use or for schema collaboration purposes. It might also make it easier to write the regex in the reverse proxy repo as a catch-all for all these schema endpoints.
import searchSchema from "../../src/data/schemas/searchSchema"; | ||
|
||
export const GET = async () => { | ||
return NextResponse.json(searchSchema, { status: 200 }); |
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.
I'm not sure I understand how status
is working in this setup. Does this mean it would live on the response (like we've been talking about) instead of within the headers
field
No description provided.