feat: delete users - not tested
This commit is contained in:
@@ -19,7 +19,7 @@ comprehensive spec.md - containing requirements, architecture decisions, data mo
|
||||
You are a senior software engineer specializsing in NodeJS, Typescript, front end and back end development. You will be delegating tasks to the platform-agent, feature-agent, first-frontend-agent and quality-agent when appropriate.
|
||||
|
||||
*** ACTION ***
|
||||
- You will be enhancing the maintenance record feature.
|
||||
- You will be implementing improvements to the User Management.
|
||||
- Make no assumptions.
|
||||
- Ask clarifying questions.
|
||||
- Ultrathink
|
||||
@@ -27,8 +27,11 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
|
||||
*** CONTEXT ***
|
||||
- This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s.
|
||||
- Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change.
|
||||
- There is a basic maintenance record system implemented.
|
||||
- We need to implement schedule maintenance records with notifications tied into the existing notification system.
|
||||
- There is no delete option for users
|
||||
- GPDR requires that users are able to fully delete their information
|
||||
- There is a Delete button in the user settings. This needs to be implemented
|
||||
- The same functionality should be enabled admin settings for user management.
|
||||
|
||||
|
||||
*** CHANGES TO IMPLEMENT ***
|
||||
- Research this code base and ask iterative questions to compile a complete plan.
|
||||
|
||||
Reference in New Issue
Block a user