Closed
Conversation
Contributor
Author
|
Hello @derianrddev , I have already completed this task. I've just waiting for your review and hopefully a merge if everything is okay. |
derianrddev
suggested changes
Apr 26, 2025
Contributor
There was a problem hiding this comment.
Hello @clintjeff2
Please fix the linter errors, resolve the conflicts and apply the other requested changes — and we’ll be ready to merge!
You can check the linter issues by running:
npm run lint| APPROVED | ||
| } | ||
|
|
||
| model Order { |
Contributor
There was a problem hiding this comment.
To keep consistency with the rest of the Prisma schema, the Order model should follow the same style:
- Use camelCase field names in Prisma (
productId,buyerAddress, etc.). - Use
@map()to map to snake_case database columns (product_id,buyer_address, etc.).
Example:
model Order {
id String @id @default(uuid())
productId String @map("product_id")
buyerAddress String @map("buyer_address")
sellerAddress String @map("seller_address")
escrowId String @map("escrow_id")
status OrderStatus @default(PENDING)
createdAt DateTime @default(now()) @map("created_at")
updatedAt DateTime @updatedAt @map("updated_at")
messages Message[]
product Product @relation(fields: [productId], references: [id])
@@map("orders")
}This will match the style used in other models like Product and User.
Update the entity, service and tests to match the new field names.
ae9d4ff to
be5c476
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Implement Order Module (CRUD + Status Update)
🛠️ Issue
📖 Description
This pull request implements a full-featured GraphQL Order module using NestJS and Prisma. It includes all key CRUD operations and a robust order status update flow using enum-based validation.
✅ Changes made
Orderentity with GraphQL schema and Prisma modelCreateOrderInput,UpdateOrderStatusInput, and enumOrderStatusgetOrdersByBuyer,getOrdersBySeller,getOrdercreateOrder,updateOrderStatusOrderStatus🧪 Testing Summary
All GraphQL queries and mutations were tested using Postman with variable-based requests, ensuring type safety and correct enum resolution in the schema.
🖼️ Media (screenshots)
1. ✅ Order Test in Postman
2. ✅ Complete Migration in Terminal
3. ✅ Orders by Buyer Address
4. ✅ Orders by Seller Address
5. ✅ Get Order by ID
6. ✅ Create Order
7. ✅ Update Order Status