WIP: JWT creation and following best practices #8

Draft
mixel wants to merge 0 commits from jwt-creation into main
Owner

Follow Best Practices:

  1. Spring security (currently disabled seen in SecurityConfig.java)
  2. Renamed Coloumn names to be more aligned with best practices
  3. Return DTO instead of User Object to request
  4. Split up DTO's into request and respond
  5. Use a Mapper class for User
    JWT:
Follow Best Practices: 1. Spring security (currently disabled seen in SecurityConfig.java) 2. Renamed Coloumn names to be more aligned with best practices 3. Return DTO instead of User Object to request 4. Split up DTO's into request and respond 5. Use a Mapper class for User JWT:
mixel added the
backend
label 2024-09-06 20:04:43 +02:00
mixel added 1 commit 2024-09-06 20:04:43 +02:00
mixel added this to the (deleted) project 2024-09-06 20:04:44 +02:00
mixel added 1 commit 2024-09-06 20:57:42 +02:00
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin jwt-creation:jwt-creation
git checkout jwt-creation

Merge

Merge the changes and update on Forgejo.
git checkout main
git merge --no-ff jwt-creation
git checkout main
git merge --ff-only jwt-creation
git checkout jwt-creation
git rebase main
git checkout main
git merge --no-ff jwt-creation
git checkout main
git merge --squash jwt-creation
git checkout main
git merge --ff-only jwt-creation
git checkout main
git merge jwt-creation
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: mixel/DocuSphere#8
No description provided.