-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add compare component #60
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can make use of v-bind in css instead of adding extra variables through style. This will make code more clean and will avoid the conflicts in users code, in case of same variable names.
</script> | ||
|
||
<style scoped> | ||
.star-field { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These properties and some of the other properties can directly be used as tailwind class. absolute inset-0 overflow-hidden
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the v-bind
would help in this case because v-bind
can only access component-level reactive properties, and cannot bind to individual elements generated within a v-for loop(as per my knowledge) or I am not getting your query properly.
For now, I've added the prefix inspira
to variable names to avoid naming conflicts.
implementation of https://ui.aceternity.com/components/compare in nuxt with more flexibility and freedom with slots.