I read somewhere that what separates a junior and a senior dev is the ability to choose the right tools for a project.
Just wanna say DaisyUI wasn't the right decision since the design complies with MaterialUI specs so I moved to vuetify π #100DaysOfCode#buildinpublic
I read somewhere that what separates a junior and a senior dev is the ability to choose the right tools for a project.
Just wanna say DaisyUI wasn't the right decision since the design complies with MaterialUI specs so I moved to vuetify π #100DaysOfCode#buildinpublic
Still failing π but at least I'm failing forward. Learning a lot.
Today I: - started fetching the data from an api - updated Pinia store using api data - started styling using DaisyUI (getting some weird flexbox issues π.
Still failing π but at least I'm failing forward. Learning a lot.
Today I: - started fetching the data from an api - updated Pinia store using api data - started styling using DaisyUI (getting some weird flexbox issues π.
The solution was actually dead simple. Turns out it was who I was overthinking things, didn't need to learn anything extra but I did (good for me π€) .
For the past two days I have been working on this site and it was supposed to be simple but pagination was a nightmare π . Planning to add more features as time goes along but I'll quit for now.
I swear this is such a complicated way to write API views π₯², and it's frustrating knowing there's classes already provided by DRF that do this for you.