How harsha12a/taskscheduler works
This is a small, client-side task tracker. A user opens the add form, enters a task name and description, and submits it to the task list; each task can then be edited or deleted. App owns the task array and passes it to the form and list components, which call its state setters for changes. The README describes only a generic React/Vite template, so no additional product capabilities or persistence are documented. The graph reflects the sampled runtime source; task data is held in React state, not an external store.
Main entry points: App.jsx App and Task State · Block.jsx Task Item · NewFile.jsx Create Task Form · EditFile.jsx Edit Task Form
Components 8
Application
- React Entry
src/main.jsx - App and Task State
src/App.jsx - Task Header
src/components/header/Header.jsx
Task List
- Task List Renderer
src/components/Body/Body.jsx - Task Item
src/components/Block/Block.jsx
Task Forms
- Create Task Form
src/components/newFile/NewFile.jsx - Edit Task Form
src/components/EditFile/EditFile.jsx
Other components
- User
Connections 13
- React Entry → App and Task State: renders
- User → App and Task State: uses
- App and Task State → Task Header: renders
- App and Task State → Create Task Form: renders when open
- App and Task State → Task List Renderer: renders with tasks
- User → Create Task Form: submits task
- Create Task Form → App and Task State: updates task state
- Task List Renderer → Task Item: renders each task
- User → Task Item: selects task action
- Task Item → Edit Task Form: renders when editing
- User → Edit Task Form: submits changes
- Edit Task Form → App and Task State: updates task state
- Task Item → App and Task State: deletes task