We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Having multiple page or layout files open makes it harder to navigate around in VS Code, due to the default naming convention in Next.js.
page
layout
VS Code now supports custom labels for files included in a pattern: https://code.visualstudio.com/updates/v1_88#_custom-labels-for-open-editors
I propose default labels for page.tsx, layout.tsx and route.ts/tsx. Here's how I've done it:
page.tsx
layout.tsx
route.ts/tsx
{ "typescript.tsdk": "node_modules/typescript/lib", "workbench.editor.customLabels.patterns": { "**src/app/**/page.tsx": "${dirname} - Page", "**src/app/**/layout.tsx": "${dirname} - Layout", "**src/app/**/route.ts": "${dirname} - API", "**src/app/**/route.tsx": "${dirname} - API" } }
None
https://twitter.com/nextjs/status/1783508313113800930
The text was updated successfully, but these errors were encountered:
Would love to take this issue, and file a PR :)
Sorry, something went wrong.
While I like the idea we do not init editor specific configurations
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
Having multiple
page
orlayout
files open makes it harder to navigate around in VS Code, due to the default naming convention in Next.js.Describe the solution you'd like to see
VS Code now supports custom labels for files included in a pattern:
https://code.visualstudio.com/updates/v1_88#_custom-labels-for-open-editors
I propose default labels for
page.tsx
,layout.tsx
androute.ts/tsx
. Here's how I've done it:Before
After
Describe alternate solutions
None
Additional information
https://twitter.com/nextjs/status/1783508313113800930
The text was updated successfully, but these errors were encountered: