Use naming conventions that are both consistent with existing patterns and descriptively clear about purpose. Follow established patterns in the codebase for similar entities while ensuring names are specific and self-explanatory.
Use naming conventions that are both consistent with existing patterns and descriptively clear about purpose. Follow established patterns in the codebase for similar entities while ensuring names are specific and self-explanatory.
Example from Prisma schema:
// Avoid this:
model Project {
// Inconsistent casing (camelCase vs PascalCase)
Dashboard Dashboard[]
actions Action[] // Inconsistent
// Generic, unclear name
SavedView SavedView[] // Too generic
}
// Prefer this:
model Project {
// Consistent casing pattern
Dashboard Dashboard[]
Actions Action[] // Consistent
// Specific, descriptive name
TableViewPreset TableViewPreset[] // Clear purpose
}
When adding new fields, models, or variables, check existing related elements and follow their naming pattern. If existing names are unclear, consider refactoring them to be more descriptive about their function and context.
Enter the URL of a public GitHub repository