Feature/ft categories on off domain#13
Merged
Merged
Conversation
… with categoryStatus
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
Phase 1 of the
ft-categories-on-offfeature — domain model extension with per-category status tracking. AddsCategoryStatusenum, extends Card entity with category status management, and creates corresponding DTOs for API layer.Changes
Domain Model
ACTIVEandINACTIVEvaluesMap<Category, CategoryStatus> categoryStatusesfieldINACTIVEDTOs
@NotNull CategoryStatus statusfieldcategoryandstatusfields, static factory from(Category, CategoryStatus)CategoryStatus categoryStatusfield (4th component)API Controller
Tests
Notes
INACTIVE; card reactivation does not restore category statuses (categories stayINACTIVEuntil explicitly activated)Checklist