LogoLogo
  • 👋Cal.com Handbook
  • The Company
    • ❓What is Cal.com?
    • 📈Mission, Vision and Values
    • 🅰️Glossary
    • 📈Organization Chart
  • HR & Careers
    • 👷Contract-to-hire trials
    • 🛫Onboarding
    • 🏆IC Levels
      • ⛰️Engineering Levels
        • 🕵️IC1 Engineer (Code Cadet)
        • 👷‍♀️IC2 Engineer (Code Craftsperson)
        • 🧘‍♀️IC3 Engineer (Code Connoisseur)
        • 🧙‍♂️IC4 Engineer (Code Wizard)
    • 💡Sharing your views
    • 💸Bonus & Equity Structure
  • Policies
    • 🏖️Vacations
    • 💳Expenses
    • 🗣️Communications
  • Engineering
    • 🔔Managing Notifications
    • ⭐Valuable Bookmarks
    • 🐛How to report issues
    • 💻How we work on Tickets
    • 🔥What to do during Emergencies
    • ✅PR Reviews
    • ☑️Self-reviews
    • 📚Keeping Docs up-to-date
    • 🌐HTTPS & Subdomains
    • 🎯Best practices
      • Data fetching
      • Avoid Prop Drilling
      • Prefer defaultHandler for simple API handlers
      • Prefer inferred types over explicit ones
      • Prefer early returns
      • Avoid comparing multiple values with `includes`
      • Validate using zod instead of type casting
      • Prefer Composition over Prop Drilling
      • Prefer ternaries over Short Circuiting “&&” for React Components
      • Don't modularize prematurely
      • Only select data you need
      • Disallowing the use of unrestricted Metadata fields
      • E2E Tests Best Practices
    • 💻Codebase
      • 🔓Keeping the lock file in sync
      • 🚫Git Private Submodules
      • 🏎️Monorepo / Turborepo
      • 🌝Deploying to Production
      • ☁️Deployment
      • 💻Debug Desktop App
      • 🚩Enabling/Disabling Features
    • 🔺Resolving failed migration on Vercel Preview
    • 🔦Cal.com Status Page
  • Customer Success
    • 💟Tone
  • Marketing
    • 🎬Media
    • ☝️How to add a new Tip to Sidebar
  • 🤲Sales
    • Operations Stack
Powered by GitBook
On this page

Was this helpful?

  1. Engineering

Best practices

Here are some of the recommendations to achieve optimal code quality and to follow best practices.

  • Data Fetching

  • Prefer inferred types over explicit ones

  • Prefer early returns

  • Avoid comparing multiple values with includes

  • Validate using zod instead of type casting

  • Don't hesitate extracting nested code into new React Components

  • Code organization tips

  • Consider state machines over simple boolean states

  • Don't extract function props outside render just because

  • Make proper user of React Children

  • Authed CRUDs should be user centric

  • Prefer adding tRPC queries over /api/.. endpoints on web

  • Prefer defaultHandler for simple API handlers

  • Prefer Composition over Prop Drilling

  • Avoid Prop Drilling

  • Prefer ternaries over Short Circuiting “&&” for React Components

TODO: Expand each of these bullet points

Additional resources

  • https://react-typescript-cheatsheet.netlify.app/docs/basic/getting-started/basic_type_example/

PreviousHTTPS & SubdomainsNextData fetching

Last updated 1 year ago

Was this helpful?

🎯