Skip to content

Dev#72

Open
mshahulpm wants to merge 44 commits into
WeCode-Community-Dev:mainfrom
mshahulpm:dev
Open

Dev#72
mshahulpm wants to merge 44 commits into
WeCode-Community-Dev:mainfrom
mshahulpm:dev

Conversation

@mshahulpm

Copy link
Copy Markdown

Description

This PR completes the MVP implementation of the project following Domain-Driven Design (DDD) and Clean Architecture principles.

Changes

  • Completed the backend MVP implementation
  • Implemented domain-driven architecture with clear separation of domain, application, infrastructure, and presentation layers
  • Added core business modules and application workflows
  • Configured database integration using Prisma and PostgreSQL
  • Completed frontend MVP with React and TypeScript
  • Integrated frontend with backend APIs
  • Implemented responsive UI for the MVP features
  • Added validation, error handling, and API documentation where applicable

Phase Category

  • Phase 1: MVP Submission (Base Foundation)
  • Phase 2/3: Feature Implementation or Modularization
  • Phase 4: Scalability Optimization
  • General (Documentation, Bugfix, Chore, etc.)

Tech Stack (For Phase 1 MVP Submissions)

(Example: Frontend: React, Backend: Node.js, Database: MongoDB)

  • Frontend: React,Typescript,zod,axios,
  • Backend: Nodejs, Nestjs with Typescript, Prisma orm
  • Database: PostgreSQL

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature / Module (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Checklist:

  • I have read the Contribution Guidelines.
  • My code follows the community spirit and standards of the WeCode community.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • My changes generate no new warnings or errors.

AI Disclosure

  • I did NOT use AI tools to generate this code.
  • I used AI tools (e.g., Copilot, ChatGPT, Claude) to help write this code, and I have fully reviewed, tested, and understand the output.

Screenshots / Screen Recording (if applicable)

mshahulpm added 30 commits June 10, 2026 20:52
- ddd and clean architecture implemented
- swagger configured
- nest js setup
- logger interface added and implemented with nestjs logger
- zod validation configured
* setup authentication and authorization infrastructure
* add auth context and provider
* implement login/logout session management
* add token storage utilities
* configure axios client with request/response interceptors
* implement authenticated user bootstrap using session API
* add user API service integration
* implement protected routes and role guards
* configure role-based routing for user, venue owner, and admin
* add role-based navigation visibility
* implement role-based post-login redirection
* add guest route protection
* fix authentication reload and session restoration issues
* integrate frontend auth flow with backend APIs
* prepare application structure for future feature modules
- list users api and command created
- common pagination class added for paginated response
chore : restored old user listing and created new user listing components for admin
- Form added to create new user
- Api function added to crate user
feat: venues listing by owner id completed
feat: venue owner section completed
 - owner listing
 - bookings listing

chore: added a datatable
feat: all bookings list for owner added
feat: booking details page added for venue owner
- api integrated
feat: booking details api completed
chore: removed unwanted tables from prisma schema

init: added seed script
chore: removed amenities and venue_amenties table and updated the code for that
fix: search venue fix only approved venues are listing
- Add public layout, landing page with hero section and featured venues
- Add venue search page with filters, sorting, and pagination support
- Add venue details page with image gallery, amenities, reviews, and booking card
- Add multi-step booking flow with date selection, guest details, and price breakdown
- Add My Bookings page with status tabs and cancel functionality
- Add Booking Details page with payment summary and cancellation dialog
- Add Favorites page for saved venues
- Add user profile page
- Add guest guard and update auth guard for role-based routing
- Register all user routes under auth/role guards
- Update VenueCard, VenueDetails, and BookingSummary types to match API response shape
- Add user-booking, user-favorites, and venue-public API service files
- Fix API response mismatches: flat address fields, string[] amenities/images, optional rating fields
- veneu image entity added
- venue image repository interface added and implemented with prisma
- File storage interface added and implemented with local file storage
- venue image upload route configured
mshahulpm added 14 commits June 23, 2026 21:30
- search venues api updated with pagination
- seed script update
- user listing component updated with data table
- data table improvements and bug fixes
- sign in form updated with error message and loading button
- consistant blue button for add
- lint warning fix
- prisma schema updated
- booking related queries and command updated with booking status
- entity and enum added
- prisma schema updated
- interface added and implemented using razorpay
- command handlers added
- nest module configures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant