Currently exploring the creation of a user schema in TypeScript. I've observed that many people use an interface which functions well until I introduce a message involving username.unique or required property.
No error code present:
import {model, models,Schema,Document } from "mongoose";
interface UserType extends Document{
username : string,
email : string,
password : string,
}
const userSchema = new Schema<UserType>({
username : {
type : String,
required : true,
trim : true,
minlength : 3
},
email : {
type : String,
required : true,
trim : true,
lowercase : true,
},
})
However, upon adding messages, a squiggle error occurs.
import {model, models,Schema,Document } from "mongoose";
interface UserType extends Document{
username : string,
email : string,
password : string,
}
const userSchema = new Schema<UserType>({
username : {
type : String,
required : [true, "Username is required"],
unique : [true, "Username is already taken"],
trim : true,
minlength : 3
},
email : {
type : String,
required :[ true, "Email is required"],
unique : [ true, "Email is already in use"],
trim : true,
lowercase : true,
},
})
Error message received:
Type '{ type: StringConstructor; required: [true, string]; unique: (string | true)[]; trim: true; minlength: number; }' is not assignable to type 'SchemaDefinitionProperty<string> | undefined'.
Types of property 'unique' are incompatible.
Type '(string | true)[]' is not assignable to type 'number | boolean | undefined'.ts(2322)
In search for an effective solution to this issue or whether utilizing a hybrid JS + TS approach is recommended. Thoughts?
*PS: Working on a next.js project*