refactor: next nest.js backend#210
Draft
GaoNeng-wWw wants to merge 18 commits into
Draft
Conversation
* feat(nest-next): project init * feat(nest-next): add i18n and exception filter * feat(nest-next): enable versioning * feat: implement permission * feat: restore pnpm-workspace.yaml * style: remove console.log, use logger
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
refactoring
* feat: menu endpoint implement * feat: approve dep build scripts * fix: restore pnpm-workspace.yaml * feat: use seeder deploy seed data
* feat(next-nest.js): role endpoint * feat: rbac seeder
* fix(next-nest/permission): find all permission filter * fix(next-nest/permission): add api-param swagger
- use cqrs and expose domain event.
* feat(next-nest/auth): v1 init * wip feat(auth): add jwt dep * feat(auth): auth v1 endpoint * feat: decorator and reject guard * feat: implement public decorator and auth guard * feat: add config jsonschama and example
* feat(auth): kickout user session if password changed or removed * fix: register RevokeAllUserSession command handler
* feat: implement lang endpoint * feat: add i18n seeder and controller
* feat: implement permission guard * feat: rbac and reject decorator
* fix(menu): remove menu * fix(menu): update menu * fix(role): permission update * style(role): remove console.log * feat(role): remove role will check user if has binding user will prevent remove action * fix(permission): allow empty description * fix: collection<UserRole> not not initialized * feat(user): add `PasswordNotMatch` error * fix(user): transform array-string to array * fix(i18): remove batch-remove-i18.dto * feat(role): better role cache * fix: prevent user create if user exists * fix: token flush fail * feat: winston nest logger * feat(mock): endpoint * feat(v1/application): application endpoint * feat: remove debugger * revert: vite.config.dev.ts * fix: typo * fix(tinyvue): review suggestion * fix: compare confirmPassword and oldPassword * fix: transactional * feat: add cn i18n record * fix: can not get accept-language * fix: remove cache * feat: singleton refresh * feat(tinyvue): name will be fallback in add-role select component * fix: remove ParseIntPipe
* feat: add v2 docker check * feat: generate new migration file * optimize: Optimize startup sequence
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
1 participant
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.
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #206
What is the new behavior?
Does this PR introduce a breaking change?
Other information