Haha I totally visualize you as a person waving your hands now.
I think my main thing is thinking out the full application on paper to help with this.
There we write out what could change for a reusable element.
But as you might know, requirements change, and this can cause hectic changes, and break for one of the things.
Just the other day created a super re-usable input component, could handle about anything, except for large file upload.
Trying to wire that into it, was just breaking about everything, so decided to deduct it, it's not neat and nice, and what you want, but sometimes it's also a good mix of time vs effort vs result.
I hope I got your question right here, also up for discussion on points like this ✌️
Ah, that also might be part of it :). My current job has a simple front end and endlessly complex back end, so I'm mostly thinking of API calls. I could totally see designing a reusable component
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Haha I totally visualize you as a person waving your hands now.
I think my main thing is thinking out the full application on paper to help with this.
There we write out what could change for a reusable element.
But as you might know, requirements change, and this can cause hectic changes, and break for one of the things.
Just the other day created a super re-usable input component, could handle about anything, except for large file upload.
Trying to wire that into it, was just breaking about everything, so decided to deduct it, it's not neat and nice, and what you want, but sometimes it's also a good mix of time vs effort vs result.
I hope I got your question right here, also up for discussion on points like this ✌️
Ah, that also might be part of it :). My current job has a simple front end and endlessly complex back end, so I'm mostly thinking of API calls. I could totally see designing a reusable component