Feat: Implemented Message Module Feature - Closing Issue#243

[Shukazuby]

📝 Pull Request Title

🛠️ Issue

• Closes [FEAT]: Implement Messages Module (GraphQL API) #243

📖 Description

• Implemented GraphQL support for sending and retrieving messages linked to orders.

✅ Changes made

• Added CreateMessageInput DTO for message creation input
• Added Message Model GraphQL object type for message output
• Created MessageService to handle database logic using Prisma
• Implemented getMessagesByOrder GraphQL query
• Implemented sendMessage GraphQL mutation
• Registered resolver and service in MessageModule

🖼️ Media (screenshots/videos)

📜 Additional Notes

[derianrddev]

Hello @Shukazuby

Just a few small adjustments needed regarding the Prisma model and unnecessary dependencies.
Once those are addressed, everything should be ready to merge!

[derianrddev]

To keep consistency with other Prisma models, please update the Message model to use camelCase field names with @map for database columns.

Example:

model Message {
  id             String   @id @default(uuid())
  orderId        String   @map("order_id")
  senderAddress  String   @map("sender_address")
  content        String
  createdAt      DateTime @default(now()) @map("created_at")
  updatedAt      DateTime @updatedAt @map("updated_at")

  order  Order @relation(fields: [orderId], references: [id])
  sender User  @relation("UserMessages", fields: [senderAddress], references: [walletAddress])

  @@map("messages")
}

Update the service and tests to match the new field names.

[derianrddev]

It looks like none of the newly added dependencies in apps/backend/package.json are necessary for this PR:

• @types/react
• @types/react-dom
• @types/lodash
• @types/trusted-types
• @types/web

Please remove them to keep the project clean.
If any of them are actually required for the work done, feel free to leave those in.

[Shukazuby]

Hi @derianrddev. Thank you, I have effected the changes

[derianrddev]

Great job! Thank you very much!