Move User
model manipulation to RPC endpoint
#3993
Labels
ready
Ready for implementation
type: enhancement
New feature or request
work: backend
Related to Python, Django, and simple SQL
work: frontend
Related to frontend code in the mathesar_ui directory
Milestone
Problem
One of our few remaining REST endpoints is
/api/ui/v0/users/
. Keeping that endpoint requires keeping around DRF, and in particular, requires keeping around our DRF error handling machinery. This adds an astonishing amount of complexity and code to our repo.Proposed solution
We should move Mathesar user-wrangling functionality to RPC functions. The current list of endponts mapped to functions (from the wiki) is:
/api/ui/v0/users/{userId}/
users.delete
/api/ui/v0/users/{userId}/
users.get
/api/ui/v0/users/{userId}/
users.patch
/api/ui/v0/users/{userId}/password_reset/
users.password.revoke
/api/ui/v0/users/
users.list
/api/ui/v0/users/
users.add
/api/ui/v0/users/password_change/
users.password.replace_own
Additional context
We elected to forgo moving these endpoints as part of the architectural transition to save time.
Tasks
users.delete
RPC function #4000users.get
RPC function #4001users.patch
RPC function #4002users.password.revoke
RPC function #4003users.list
RPC function #4004users.add
RPC function #4005users.password.replace_own
RPC function #4006The text was updated successfully, but these errors were encountered: