Repository navigation
test: set up vitest and cover auth and users - #2
Merged
Merged
Conversation
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.
What changed
@nestjs/typeorm12 and TypeORM 1 ship as ESM only, which Jest couldn't load; Vite handles them, and SWC emits the decorator metadata Nest's dependency injection needs.AuthService(duplicate email returns 409, Argon2id hash stored, hash never returned,validateUser,login),UsersServicewith a mocked repository, the controllers and the password rules inCreateUserDTO./auth/profile, plus 409 on a duplicate email and 401 on a wrong password or a missing token.@IsStrongPasswordalready required a symbol by default, but the message didn't say so, soSecret123failed with an error that didn't explain why. The rule is now explicit and the message mentions the symbol. The README examples useSecret123!.buildjob now runslint:check, the unit tests and the build; a newe2ejob runs the end-to-end test against a PostgreSQL 18 service container.How to check