When Is it time to make the component wet and give up on ternaries?
https://github.com/diffim/diffinlist
https://diffinlist.vercel.app
Check out the Section.tsx component and how its implemented along with SectionCard.tsx, because of typesafety and different fetches I had to do the .map part of the component as children, yet I dont feel like this is very dry. Also there are a lot of ternaries in that component for things that only happen once. Should I just make the codebase wet and make a different componrnt for each different fetch/section? Like I.e for the landing page make <AllPlaylistsSection> as the project grows it feels more hectic to maintain this component as I keep having to add more ternaries. Or is this normal and I should just continue.
https://diffinlist.vercel.app
Check out the Section.tsx component and how its implemented along with SectionCard.tsx, because of typesafety and different fetches I had to do the .map part of the component as children, yet I dont feel like this is very dry. Also there are a lot of ternaries in that component for things that only happen once. Should I just make the codebase wet and make a different componrnt for each different fetch/section? Like I.e for the landing page make <AllPlaylistsSection> as the project grows it feels more hectic to maintain this component as I keep having to add more ternaries. Or is this normal and I should just continue.
GitHub
FULL refactor of my diffinplaylist repo with the t3 stack! - GitHub - diffim/diffinlist: FULL refactor of my diffinplaylist repo with the t3 stack!
Was this page helpful?
