Is this way of creating reusable components a bad practice in svelte? #10495
Unanswered
cleytoncarvalho
asked this question in
Q&A
Replies: 1 comment
-
This feels like the wrong abstraction for components. Might have been better if you just used a seperate anchor and button. YMMV. See Goodbye Clean Code. Svelte's lint/a11y checks also help you better that way. Also, see skeleton.dev for pointers for theming at tailwind level instead of components and melte-ui has nice patterns about pragmatic unstyled components. Also here are someone's thoughts about @apply in Tailwind. Maybe use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I'm creating components like these bellow inspired by shadcn ui components library. But I was wondering if this is a bad practice in Svelte to create components like this and if there is problems related with performance that I should be worried about.
Beta Was this translation helpful? Give feedback.
All reactions