♻️ Regenerate client to use UUID instead of ID integers and update frontend #1281
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.
Description
Problem:
Previously, the
deleteEntity
function was designed to handle IDs as numbers. After updating the ID format to UUIDs (strings), the function's type handling needed adjustment to correctly process these new string-based IDs.Solution:
The function
deleteEntity
was modified to handle IDs as strings. The fix ensures compatibility with UUIDs and correctly routes the deletion request based on the entity type.Changes Made
Type Update:
id
parameter type fromnumber
tostring
to accommodate UUIDs.Function Logic:
ItemsService.deleteItem
with anid
parameter of typestring
.UsersService.deleteUser
withuserId
as astring
.type
is unexpected.Code Changes