Architecture Decision Records
Each non-trivial design decision in yew-nav-link is captured as a
short MADR-style document. Decisions are append-only — a record
is never edited after its status moves to accepted. Reversals are
expressed as new ADRs that mark the prior record superseded by NNNN.
Index
| ID | Title | Status |
|---|---|---|
| 0000 | Record architecture decisions | accepted |
| 0001 | class and active_class are &'static str | accepted |
| 0002 | Drop the macros feature in 0.9.0 | accepted |
| 0003 | NavError is #[non_exhaustive] from 0.10.0 | accepted |
| 0004 | Render a manual <a> instead of wrapping yew_router::Link | accepted |
| 0005 | Active NavLink emits aria-current="page" | accepted |
When to write an ADR
Write one when the answer to “why is it this way” is non-obvious and
would not be derivable from reading the code alone. Renaming a field is
not an ADR. Choosing &'static str over AttrValue is an ADR.
Template
Copy 0000-record-architecture-decisions.md as a starting point. Keep
each record to roughly one screen — context, decision, consequences. The
goal is to read fast and rot slowly.