summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Sarah Rainsberger <sarah@rainsberger.ca> 2023-08-18 19:32:10 -0300
committerGravatar GitHub <noreply@github.com> 2023-08-18 19:32:10 -0300
commitfd6261dad4f62287f17beff1f767508291a01c15 (patch)
tree3efaaf0183bac6c6ac8db1e3b2b594d8ab10651c
parent81545197a32fd015d763fc386c8b67e0e08b7393 (diff)
downloadastro-fd6261dad4f62287f17beff1f767508291a01c15.tar.gz
astro-fd6261dad4f62287f17beff1f767508291a01c15.tar.zst
astro-fd6261dad4f62287f17beff1f767508291a01c15.zip
[docs] update scopedStyleStragegy default and description (#8148)
-rw-r--r--packages/astro/src/@types/astro.ts4
1 files changed, 2 insertions, 2 deletions
diff --git a/packages/astro/src/@types/astro.ts b/packages/astro/src/@types/astro.ts
index d2475ec7d..1198b26be 100644
--- a/packages/astro/src/@types/astro.ts
+++ b/packages/astro/src/@types/astro.ts
@@ -608,7 +608,7 @@ export interface AstroUserConfig {
* @docs
* @name scopedStyleStrategy
* @type {('where' | 'class' | 'attribute')}
- * @default `'where'`
+ * @default `'attribute'`
* @version 2.4
* @description
*
@@ -619,7 +619,7 @@ export interface AstroUserConfig {
*
* Using `'class'` is helpful when you want to ensure that element selectors within an Astro component override global style defaults (e.g. from a global stylesheet).
* Using `'where'` gives you more control over specifity, but requires that you use higher-specifity selectors, layers, and other tools to control which selectors are applied.
- * Using `'attribute'` is useful in case there's manipulation of the class attributes, so the styling emitted by Astro doesn't go in conflict with the user's business logic.
+ * Using 'attribute' is useful when you are manipulating the `class` attribute of elements and need to avoid conflicts between your own styling logic and Astro's application of styles.
*/
scopedStyleStrategy?: 'where' | 'class' | 'attribute';