From 336b73b80b7569b0954cbac17b71f0e8d09fc4b8 Mon Sep 17 00:00:00 2001
From: Zeeshan Tamboli <zeeshan.tamboli@gmail.com>
Date: Fri, 24 Jun 2022 20:43:38 +0530
Subject: [PATCH] [docs] Add note in docs about `componentsProps.root` taking
 precedence (#33097)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* docs

* docs wording

* run CI

* Update docs/data/base/getting-started/usage/usage.md

Co-authored-by: Michał Dudak <michal.dudak@gmail.com>

Co-authored-by: Michał Dudak <michal.dudak@gmail.com>
---
 docs/data/base/getting-started/usage/usage.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/data/base/getting-started/usage/usage.md b/docs/data/base/getting-started/usage/usage.md
index 8b801882a9612d..3bc4fb6936af45 100644
--- a/docs/data/base/getting-started/usage/usage.md
+++ b/docs/data/base/getting-started/usage/usage.md
@@ -85,6 +85,10 @@ These two examples are equivalent:
 <BadgeUnstyled componentsProps={{ root: { id: 'badge1' } }}>
 ```
 
+:::warning
+If both `componentsProps.root` and additional props have the same keys but different values, the `componentsProps.root` props will take precedence. This does not apply to classes and the `style` prop (they will be merged instead).
+:::
+
 ## Components vs. hooks
 
 MUI Base includes two kinds of building blocks: **components** and **hooks**.