Category Controller

[ChoaibMouhrach]

• index

  • Search
    • id
    • by name
  • Sort
    • id
    • name
  • Order
    • desc
    • inc
  • Fields
    • id
    • image
    • name

• store

  • image
  • name

• update

  • image
  • name

• destroy

• Testing

  • index
    • sort
    • fields
  • store
  • update
  • delete

[ID-JA]

@PACY2

https://github.com/PACY2/eco/blob/d1edc0fa66598bec406970e99c381db1a3415462/server/controllers/categoryController.ts#L119
when an item is deleted from the database, it is permanently removed, which can be problematic if we need to recover it later. By implementing a soft delete feature, we can change the status of the deleted item to indicate that it has been deleted, but still keep the item in the database. This way, we can recover it if needed.

There are different ways to implement soft delete but one common approach is to add a deletedAt field to the database table. When an item is deleted, we would update the deletedAt field with the current timestamp, but the item would still exist in the database. Then, when querying the database, we would exclude items that have a non-null deletedAt value.

const categorySchema = new Schema({
  name: {
    type: String,
    required: true,
    unique: true,
    dropDups: true
  },
  image: String
+ deletedAt: { type: Date, default: null }
})