refactor(components): [carousel] class optimization in code #14954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please make sure these boxes are checked before submitting your PR, thank you!
dev
branch.Description
🤖[deprecated] Generated by Copilot at 88bf522
Refactored the class binding logic of the
carousel-item
component to use a computed property. This made the code more readable and maintainable.Related Issue
Fixes #___.
Explanation of Changes
🤖[deprecated] Generated by Copilot at 88bf522
:class
binding ofcarousel-item
component by using computed propertyitemKls
(link)itemKls
computed property insetup
function ofcarousel-item
component (link)ns
utility to generate class names withel-
prefix andis
andem
modifiers (link)value
property ofref
objects to access reactive values ofactive
,inStage
,hover
, andanimating
(link)isCardType
andisVertical
props foritemKls
computed property (link)