What should we do with the default core_components file from the Phoenix 1.7
#322
andyduong1920
started this conversation in
RFCs
Replies: 2 comments 1 reply
-
|
I voted "Tailwindcss addon selected - Option 2" 🙌 IMO, we should keep the CoreComponents module as the template may be used by various types of applications. Thus we should keep this in case some projects such as the admin panel, or back-office app, won't need much custom styling or branding. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yeah make sense @hanam1ni 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I realized the Vote doesn't allow multiple selections, so I updated the vote content a bit FYI |
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
-
As you might be aware, Phoenix 1.7 will generate the CoreComponents file, which contains most of the components like
input, form, button, ...using Tailwindcss.Most of our project requires custom CSS. So I'm asking your opinion about when the user selected the TailwindCSS addon.
Btw, if the user selects the Bootstrap addon, we can remove the CoreComponent as it's useless
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions