docs(Carousel): add caveat about inject styles

juntossomosmais · Aug 9, 2023 · 0287647 · 0287647
1 parent 8a236a6
commit 0287647
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/.../architecture-decision-records/0012-why-have-a-carousel-with-swiper.stories.mdx b/.../architecture-decision-records/0012-why-have-a-carousel-with-swiper.stories.mdx
@@ -25,3 +25,6 @@ The [Swiper](https://swiperjs.com/)  was the only option considered.
 ## Decision
 We have decided to use Swiper as our Carousel component library, once it match our requirements and we have a previous knowledge, doing a internal wrapper to maintain the Atomium signature.
 
+
+## Caveats
+An important point to keep in mind is the need of use the [injectStyles](https://swiperjs.com/element#injecting-styles) from Swiper if it is needed to overwrite or add new styles to inside of Swiper Element Shadow Dom.
diff --git a/.../architecture-decision-records/0013-why-using-virtual-carousel-item.stories.mdx b/.../architecture-decision-records/0013-why-using-virtual-carousel-item.stories.mdx
@@ -17,8 +17,8 @@ Then we need to convert each `atom-carousel-item` into `swiper-slide`.
 ## Considered Options
 To convert the inner `<atom-carousel-item>` to `<swiper-slide>`, and we have two options:
 
-- Create and `atom-carousel-item` component and inside itself creating the `<swiper-slide>` component on parent and them self deleting from parent.
-- The parent itself convert all children at once.
+1. Create and `atom-carousel-item` component and inside itself creating the `<swiper-slide>` component on parent and them self deleting from parent.
+2. The parent itself convert all children at once.
 
 ## Decision Drivers