Frontend
a11y-0.0.1
a11y-0.0.11.0.0
a11y-0.0.1
a11y-0.0.11.0.0
  • Introduction
  • Project Guidelines
    • INTRODUCTION
    • PROJECT SETUP
      • Project starter
      • Static type checking
      • Code Quality Tools
      • Enforcing good practices
      • Testing
      • Code versioning flow
      • Continuous Integration & Delivery
      • Isolated component development
    • EFFECTIVE AND CONSISTENT WORKFLOW
      • Code structure, architecture
      • Code versioning and review flow
      • Testing
      • Static type checking
      • Continuous Integration & Delivery
      • Dependency checking
      • Project Management Tools
      • Communication
    • THE QUALITY OUTPUT
      • Great UX/UI
        • User Experience
        • Responsive Web Design
        • SEO, SMO
        • Progressive Web Apps
      • Stability
        • Documentation
        • Analytics & Error Tracking
        • Quality Assurance
      • Performance
        • Bunde Size
        • Deployment
        • Audits & Reports
      • Security
      • Accessibility
        • Why a11y?
        • Fundamentals
        • User stories
        • A11y tools
        • Checklist
    • FINAL WORDS
Powered by GitBook
On this page

Was this helpful?

  1. Project Guidelines
  2. EFFECTIVE AND CONSISTENT WORKFLOW

Static type checking

PreviousTestingNextContinuous Integration & Delivery

Last updated 5 years ago

Was this helpful?

has quite the same story (mentioned in the Project Setup chapter) and importance like the testing mentioned above.

Besides guarding your types, type checking is also great for making a better developer experience (better IntelliSense, code analysis). You can also autogenerate types (for example, from GraphQL schemas). Doing refactoring is much easier.

Your workflow is much more efficient with typing. Even though it takes some time to get used to it.

Type checking