feat(carousel): add carousel component

[theo-matzavinos]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] The commit message follows our guidelines: https://github.com/goetzrobin/spartan/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Other... Please describe:

Which package are you modifying?

• [ ] accordion
• [ ] alert
• [ ] alert-dialog
• [ ] aspect-ratio
• [ ] avatar
• [ ] badge
• [ ] button
• [ ] calendar
• [ ] card
• [ ] checkbox
• [ ] collapsible
• [ ] combobox
• [ ] command
• [ ] context-menu
• [ ] data-table
• [ ] date-picker
• [ ] dialog
• [ ] dropdown-menu
• [ ] hover-card
• [ ] input
• [ ] label
• [ ] menubar
• [ ] navigation-menu
• [ ] pagination
• [ ] popover
• [ ] progress
• [ ] radio-group
• [ ] scroll-area
• [ ] select
• [ ] separator
• [ ] sheet
• [ ] skeleton
• [ ] slider
• [ ] switch
• [ ] table
• [ ] tabs
• [ ] textarea
• [ ] toast
• [ ] toggle
• [ ] tooltip
• [ ] typography

What is the current behavior?

Closes #117

What is the new behavior?

Does this PR introduce a breaking change?

• [ ] Yes
• [ ] No

Other information

[theo-matzavinos]

One thing I'd might change is the directives for the buttons to become: hlmCarouselPrevious and hlmCarouselNext.

They're actually components which is why I opted for the kebab-case selector. I've borrowed this idea from material/cdk. I have no strong feelings about it though.

Some notes/questions:

1. I didn't exactly follow shadcn's implementation and moved the scroll container to the root component. It was easier to implement this way especially since in shadcn they forward the classes to the inner div.
2. Should I change the icons to lucide?
3. There's really no logic since it's a helm component. Do we need to test anything?

Looking forward to your feedback.

[goetzrobin]

One thing I'd might change is the directives for the buttons to become: hlmCarouselPrevious and hlmCarouselNext.

They're actually components which is why I opted for the kebab-case selector. I've borrowed this idea from material/cdk. I have no strong feelings about it though.

Some notes/questions:

1. I didn't exactly follow shadcn's implementation and moved the scroll container to the root component. It was easier to implement this way especially since in shadcn they forward the classes to the inner div.
2. Should I change the icons to lucide?
3. There's really no logic since it's a helm component. Do we need to test anything?

Looking forward to your feedback.

Maybe we can add both selectors? You can have multiple selectors separated by a comma.

1. I don't have any problems with that! Seems like a reasonable change
2. Yes please that would be great!
3. No tests needed for helm if they don't include any logic. Maybe add a sanity e2e test that just ensures the basic functionality works?

[goetzrobin]

@theo-matzavinos Let me know if that gives you everything you need or if there's anything I can do to help you!

[theo-matzavinos]

Maybe we can add both selectors? You can have multiple selectors separated by a comma.

That's reasonable. I should use the camelCase selectors in the docs then?