Conversation
* chore(drizzle):feat(database): setup database lib / configure drizzle * chore(db): generate initial migration
* chore: update eslint configuration * chore: add husky and lint-staged configuration * chore: add prettier configuration * chore: add CI workflow and .env.example * chore: bump per reviewer requests * chore: remove workflow
* chore: add lint staged * chore: remove jest and add vitest deps * chore: add vitest.config.ts * chore: update scripts for testing * chore: add vitest global types to tsconfig * chore: migrate e2e tests configuration to vitest * chore: fix eslint globals and include test folder in tsconfig * chore: format code with prettier
* feat(infra): setup multi-stage dockerfiles and compose orchestration * chore: resolve merge conflicts
…trap * feat(infra): setup multi-stage dockerfiles and compose orchestration * chore: resolve merge conflicts * chore: add api boilerplate packages * feat(bootstrap): implement unified bootstrap service and fix fastify issues * feat(bootstrap): implement zod ecosystem contracts
* ci: add docker build check workflow * docs(gh): setup issue templates and community configuration
* docs: add README with stack and quick start guide * docs: add contributing guidelines with development standards * chore: bump per reviewer requests
* docs(contributing): add chore to allowed commit types * chore: setup husky, commitlint and lint-staged * chore: change lint-staged config from json to mjs
…infra * feat: add users module and standardized API error responses * feat: core domain entity type / add service and repository * chore: add auth module arch * feat(shared): add ApiBaseController decorator for global swagger responses * feat(swagger): add reusable swagger error decorators * docs(users): describe user api endpoints in swagger * feat(auth): scaffold auth controller with route stubs * feat(auth): scaffold auth service with dependencies * feat(auth): add zod-based dtos for authentication and 2fa * refactor(swagger): rename ApiRequireAuth to ApiUnauthorized for better reuse * docs(auth): describe auth api endpoints in swagger * chore: feat libs per auth flow / rename endpoints * chore: feat per auth module libs and redis * feat(auth): intergrate with jwt module and update config module * feat(redis):chore(infra): integrate redis and setup correct infra * feat(auth):chore(ua-parser): integrate logic per register flow #1 * feat(auth): integrate logic per sign flow #2 * feat(mail): add mail module and Handlebars templates * feat(user): implement user controller with facade integration * feat(auth): integrate logic per reset password flow #3 / bug with otplib always code apply * fix(auth): fix OTP verification bypass in AuthService * fix(auth): correct session expiration time in signIn and verify * fix(email): fix verification code copy formatting * fix(infra): specify postgres user and db for healthcheck * fix(cors): normalize origins to hostname to resolve local blocks * fix(compose): resolve error with depends and correct output per users * feat(s3):chore(aws): add s3 module at libs and env file * refactor(auth): fix type inconsistencies in user models * feat(infra): setup migrations, optimize pg pool, and add ghcr workflow * chore(auth): add password reset and sign-up confirmation Swagger documentation * feat(user): implement avatar upload functionality with S3 integration * chore(auth): add password reset and sign-up confirmation Swagger documentation --------- Co-authored-by: Maksym Berehovyi <108676512+maksberegovoi@users.noreply.github.com> Co-authored-by: Maxim <darlinggbm@gmail.com>
* chore(team): integrate base snippets per module * feat(teams): implement team management core with RBAC and metadata * refactor(user): extract file upload logic into custom decorator * feat(teams): implement core structure, entities and swagger documentation * feat(teams): implement team tags and paginated retrieval * feat(teams): add media module for team avatar and banner uploads * feat(teams): implement team invitation email template and logic * feat(teams): implement core logic and repository methods for team membership * feat(teams): add team invitation event and processing logic * feat(teams): implement invitations flow and refactor members repository * chore(fastify-csrf): implementation of core infrastructure, logging and error filters --------- Co-authored-by: Maxim <darlinggbm@gmail.com>
* chore(projects): initialize module boilerplate * feat(projects): implement data access layer and database schema * chore: update dependencies, add tests and enhance swagger styling * feat(projects): implement CRUD, Swagger documentation and Zod validation * refactor(teams): restructure team routes and modularize architecture * refactor: split projects and teams into specialized controllers * refactor(auth): split access and recovery controllers and fix bug * refactor(user): separate profile and settings logic / bump bug with imports * chore: restructure services and use type-only imports * feat(project): add service logic, update entity and format code * refactor(core): unify exception filter and resolve technical debt (#22) * refactor(core): unify exception filter and resolve technical debt * refactor: finalize unified error handling and sync test suites
…nd decline functionalities (#34)
…cker fixes #32 * feat(infra): setup pnpm workspaces and initialize k6 load testing structure * feat(infra): setup pnpm workspaces and initialize k6 load testing structure * feat(auth): add user seeding and load testing for auth endpoints (#37) * feat(auth): add user seeding script for k6 * feat(auth): implement load testing for SIGN-IN, SIGN-OUT, REFRESH endpoints * test(load-test): refactor infrastructure and expand user scenarios * feat(load-test): rename seed script and update script name in package.json * feat(load-test): move sign-in logic into separate module for reusability * feat(load-test): add scenarios for user endpoints and update seeding * feat(load-test): expand team scenarios and enhance data seeding * chore(load-test): update config and client * refactor(load-test): simplify scenarios by using centralized ApiClient * chore(load-test): enhance db seeding with teams and tags, separate seed and clear * feat(load-test): add teams load testing scenarios for teams.controller endpoints * feat(load-test): rename seed script and add redis seed * feat(load-test): rename client to api-client and add redis-client * feat(load-test): implement load testing for projects module (#48) * feat(k6): separate clearing and seeding data for load tests and add script for clearing * feat(docker): set CI environment variable in production Dockerfile --------- Co-authored-by: Maksym Berehovyi <108676512+maksberegovoi@users.noreply.github.com>
* refactor: pass app to global scope * refactor(auth): implement DDD architecture and layer separation (#49) * refactor(user): migrate to DDD hexagonal architecture and update cros… (#51) * refactor(user): migrate to DDD hexagonal architecture and update cross-module imports * refactor(tests): resolve conflicts test e2e * refactor: apply DDD to teams module and update cross-module imports (#52) * feat(projects): implement access validation policy and refactor to DDD hexagon (#53) * refactor: cleanup use-cases, optimize imports and move media to shared * refactor(database): move migration logic from shared to database lib * feat: migrate all API modules to DDD and fix auth issues * refactor(teams): overhaul invitation flows
* fix(teams): integrate MailProcessor into TeamsModule and app.module * fix(teams): set TTL for team and user invites in invitation handling
…cific settings (#57) fix(auth): enhance refresh token cookie handling with environment-specific setting
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.
No description provided.