refactor: Standardize type naming conventions and file casing for course and category types.
This commit is contained in:
parent
6bbbde062a
commit
057f640272
6 changed files with 7 additions and 26 deletions
|
|
@ -1,19 +0,0 @@
|
|||
import { Course, Prisma } from '@prisma/client';
|
||||
|
||||
// Use Prisma's CourseCreateInput for creating courses
|
||||
|
||||
// Response type uses Prisma's Course model
|
||||
|
||||
|
||||
export interface listCourseResponse {
|
||||
code: number;
|
||||
message: string;
|
||||
data: Course[];
|
||||
total: number | null;
|
||||
}
|
||||
|
||||
export interface getCourseResponse {
|
||||
code: number;
|
||||
message: string;
|
||||
data: Course | null;
|
||||
}
|
||||
|
|
@ -12,7 +12,7 @@ export interface Category {
|
|||
updated_at: Date | null;
|
||||
}
|
||||
|
||||
export interface listCategoriesResponse {
|
||||
export interface ListCategoriesResponse {
|
||||
code: number;
|
||||
message: string;
|
||||
data: {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue