Skip to content

Latest commit

ย 

History

History
97 lines (70 loc) ยท 1.9 KB

File metadata and controls

97 lines (70 loc) ยท 1.9 KB

Web

This document defines the conventions, file structure, and best practices to be followed


๐Ÿ“ Project Structure

as./src/
โ”œโ”€โ”€ api
โ”‚ โ”œโ”€โ”€ api.ts # API 
โ”œโ”€โ”€ components
โ”‚ โ””โ”€โ”€  # Reusable UI components 
โ”œโ”€โ”€ helper
โ”‚ โ””โ”€โ”€  # General-purpose helper functions
โ”œโ”€โ”€ hooks
โ”‚ โ””โ”€โ”€  # Custom React hooks
โ”œโ”€โ”€ lib
โ”‚ โ””โ”€โ”€  # Third-party libraries or wrappers
โ”œโ”€โ”€ main.tsx # App entry point
โ”œโ”€โ”€ pages
โ”‚ โ”œโ”€โ”€ App.module.css # Styles for the main App
โ”‚ โ””โ”€โ”€ App.tsx # Root component
โ”œโ”€โ”€ services
โ”‚ โ””โ”€โ”€  #  service layer
โ”œโ”€โ”€ styles
โ”‚ โ””โ”€โ”€  # Global and shared styles
โ”œโ”€โ”€ utils
โ”‚ โ””โ”€โ”€  # Utility functions
โ””โ”€โ”€ vite-env.d.ts # TypeScript definitions for Vite

๐Ÿง  Naming Conventions

๐Ÿ”ง Functions

  • Use CamelCase (PascalCase) for function names.

eg-

function FetchUserProfile() { ... }
function HandleLoginResponse() { ... }

Here is the updated README.md for your exp-file project, now including the full folder structure under ./src/:

๐Ÿงฎ Variables

  • Use smallCamel (camelCase) for variable names.
let userToken: string;
const isProfileComplete = true;

๐ŸŽจ CSS / SCSS / Modules

  • Use kebab-case for file and class names.
  • Prefer CSS Modules for component styles.
/* App.module.css */
.header-container { ... }
.login-form__input--focused { ... }

๐Ÿ“ Folder & File Naming

  • Use kebab-case for folder and file names.
  • Group logically related files in folders.
components/
  โ””โ”€โ”€ user-card/
      โ”œโ”€โ”€ user-card.tsx
      โ””โ”€โ”€ user-card.module.css

โš™๏ธ Code Best Practices

  • DRY: Donโ€™t Repeat Yourself.
  • Modularize: Component, Logic, API, Utility separation.
  • Use TypeScript for all files (.tsx / .ts).
  • Write meaningful commit messages.