[docs] update scopedStyleStragegy default and description (#8148)
This commit is contained in:
parent
81545197a3
commit
fd6261dad4
1 changed files with 2 additions and 2 deletions
|
@ -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';
|
||||
|
||||
|
|
Loading…
Reference in a new issue