How ragulkannadasan/workspace works
This repository contains several small web projects; the available source evidence describes the Todo app, so the graph focuses on its user-to-result workflow. Users add tasks, manage pending and completed lists, and retain task state in browser storage. The app also registers a service worker for offline-capable use. Other projects appear in the file tree, but their behavior is not represented because their source was not sampled.
Main entry points: Todo.jsx Task controller · App.jsx App shell · main.jsx React entry · TodoInput.jsx Task input
Components 10
Task management
- Task controller
todo/src/Components/Todo.jsx - Task input
todo/src/Components/TodoInput.jsx - Pending list
todo/src/Components/Pending.jsx - Completed list
todo/src/Components/Completed.jsx
Browser runtime
- React entry
todo/src/main.jsx - Local storage
- Service worker
Other components
- User
Connections 12
- User → React entry: opens app
- React entry → App shell: renders
todo/src/main.jsx - React entry → Service worker: registers
todo/src/main.jsx - App shell → Navbar: renders
todo/src/App.jsx - App shell → Task controller: renders
todo/src/App.jsx - Task controller → Local storage: reads and writes
todo/src/Components/Todo.jsx - Task controller → Task input: renders
todo/src/Components/Todo.jsx - Task input → Task controller: submits task
todo/src/Components/TodoInput.jsx - Task controller → Pending list: renders tasks
todo/src/Components/Todo.jsx - Pending list → Task controller: invokes task actions
todo/src/Components/Pending.jsx - Task controller → Completed list: renders tasks
todo/src/Components/Todo.jsx - Completed list → Task controller: invokes task actions
todo/src/Components/Completed.jsx