ADR Overview

Introduction

Architectural decision records are a record of design decisions we have made in the past because we belived they would help our code quality over time. Any ADR can be challenged, but two conditions must be met to change an ADR:

1. The proposed solution must provide a tangible benefit in terms of code quality.
2. The benefits of the proposed solution must outweigh the effort of retroactively changing the entire codebase. One such example is the decision to re-write Unleash to TypeScript.

Overarching ADRs

These ADRs describe decisions that concern the entire codebase. They apply to back-end code, front-end code, and code that doesn't neatly fit into either of those categories.

• Domain language
• Separation of request and response schemas

Back-end ADRs

We are in the process of defining ADRs for the back end. At the time of writing we have created the following ADRS:

• Naming
• Preferred export
• Breaking DB changes
• POST/PUT API payload
• Specificity in database column references
• Write model vs Read models
• Frontend API Design

Front-end ADRs

We have created a set of ADRs to help guide the development of the front end:

• Component naming
• Interface naming
• Preferred component props usage
• Preferred export
• Preferred function type
• Preferred styling method
• Preferred data mutation method
• Preferred data fetching method
• Preferred folder structure
• Preferred form architecture
• OpenAPI SDK generator