"Universal ID" was initially designed as a networking concept to avoid transmitting multiple properties individually (project ID & user ID). Due to various migrations, the concept has leaked into business logic and is now used in the Service and Repository layers.
Detailed overview
The symbol search still finds many uses for universalId in the code.
After the functions using universal ID have been replaced with functions requiring UserId directly, it will be possible to move the universalId conversion function out of UserId and into the network mapper.
Hint/location:
1. API mapper: com/appifyhub/monolith/features/user/api/UserMapper.kt
2. UserId: com/appifyhub/monolith/features/user/domain/model/UserId.kt
List the acceptance criteria
Universal ID is not used in the Service or Repository layers
Universal ID conversions are happening in the API mapper
All tests are updated to reflect this change, and passing
Provide a brief summary of the planned work
"Universal ID" was initially designed as a networking concept to avoid transmitting multiple properties individually (project ID & user ID). Due to various migrations, the concept has leaked into business logic and is now used in the Service and Repository layers.
Detailed overview
The symbol search still finds many uses for
universalIdin the code.After the functions using universal ID have been replaced with functions requiring
UserIddirectly, it will be possible to move theuniversalIdconversion function out ofUserIdand into the network mapper.Hint/location:
List the acceptance criteria
Include any additional notes (optional)
No response