---
# System prepended metadata

title: Style Override API
tags: [pitch]

---

---
robots: noindex, nofollow
tags: pitch
---


# Style Override API

### Problem
Overridding styles creates several issues for applications:
1. Performance is degraded
2. Future theme updates don't work well
3. Reduces developer efficiency over time:
    - Complex and confusing
    - Debugging
    - Maintaining

### Appetite
It is clear across v0 and v7 that developers gravitate toward style overrides.  See if there is a way to "pave the cow path" so that style overrides are simple to write and understand, performant, themeable, debuggable, and easy to maintain.

<img src="https://i.imgur.com/2Sr0zk1.jpg" width=400 />


### Solution
Start with the minimum API and introduce:
- Memoization / caching plus smart recalculation logic
- Ensure styles receive sufficient tokens to be fully themed
- Ensure CSS in JS debugger works with overrides
- Fix complication, indirection, and maintenance issues by allowing styles to be directly placed inline

### Risks (Rabbit holes)

Styles seem to be closer to "component internals" and possibly should not be leaked since it scatters internal dependencies.

[code snippet]

### Out of scope (No-gos)

- Composing new components
- Creating new styles and tokens
- Creating THE single way of styling