Repository navigation
Conversation
…fields firstName, lastName, and confirmPassword are multi-word camelCase fields. They must be serialised as first_name, last_name, and confirm_password in the JSON contract, consistent with every other compound field across the DTOs (see UserResponse, ProductResponse, CategoryResponse, etc.). Single-word fields (username, email, password) need no annotation because their Java name and the JSON key are identical.
Aligns the endpoint name with the kebab-case convention used by all other multi-word paths in this project (forgot-password, reset-password). The new path /api/v1/auth/activate-account is also more self-describing for a client consuming the API.
Keeps the endpoint publicly accessible (no authentication required) under its new path /api/v1/auth/activate-account.
The frontend route receiving the activation token is renamed from /auth/activate to /auth/activate-account to match the backend endpoint path change.
Covers all resource groups: Auth (register, login, logout, me, activate-account, forgot-password, reset-password), Categories, Products, Customers, Orders, Users, Roles, Permissions. Base environment defines baseUrl (http://localhost:8080) and an empty token variable to be filled after login. Register body uses snake_case keys (first_name, last_name, confirm_password) consistent with the @JsonProperty contract.
feat(user-management): snake_case RegisterRequest, activate-account endpoint, validation constraints
docs: add Insomnia collection
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.
Summary
feature/user-management(PR feat(user-management): snake_case RegisterRequest, activate-account endpoint, validation constraints #24):@JsonPropertysnake_case onRegisterRequest(first_name,last_name,confirm_password), activation endpoint renamed to/activate-account, custom validation constraints (@ValidPassword,@PasswordsMatch,@Unique),firstName/lastNameonAppUserfeature/docs(PR docs: add Insomnia collection #25): Insomnia collectionspring-boot-tutorial.insomnia.yamlcovering all API endpointsTest plan