-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Divyansh Bhardwaj edited this page Oct 8, 2025
·
13 revisions
Welcome to the class-notes wiki!
- Project Architecture
- Component Hierarchy
- Package Structure
- Data Models
- Local Storage Schema
- Testing Strategy
- Git Workflow
- Component Development Order
- Always start with tests - Write tests before implementing components
- Use TypeScript - Define proper types for all props
- DaisyUI classes - Prefer DaisyUI component classes over custom styles
- Accessibility - Include proper ARIA labels and semantic HTML
- Responsive - Use Tailwind responsive prefixes (sm:, md:, lg:, xl:)
- Props destructuring - Destructure props in function signature
- Default props - Provide sensible defaults where appropriate
- Export pattern - Use named exports from index.ts files
Each component should have:
ComponentName/
โโโ ComponentName.tsx # Main component
โโโ ComponentName.types.ts # TypeScript types
โโโ ComponentName.test.tsx # Tests (in __tests__ folder)
โโโ index.ts # Barrel export
For each component, test:
- Rendering - Does it render with required props?
- Props - Are all props handled correctly?
- Events - Do event handlers work?
- Conditional rendering - Are conditionals working?
- Edge cases - Empty states, null values, etc.
- Accessibility - Proper roles, labels, keyboard navigation
- Choose a component from the development order
- Review the Component Templates for the component structure
- Write tests first based on the component requirements
- Implement the component following the structure
- Ensure tests pass
- Create a pull request
Good luck with your implementation! ๐
Last Updated: October 2025
Project Version: 1.0.0
React Version: 19
Maintained by: Divyansh Bhardwaj