Interactive-rating-component

What are you most proud of, and what would you do differently next time?

I'm most proud of my ability to refactor repetitive code and create more reusable functions. For instance, I realized that I was repeatedly using similar code for handling elements and events, so I started using loops like forEach to make the process more efficient. This helped me write cleaner code that was easier to maintain. If I were to do things differently next time, I'd plan more thoroughly before starting the code to ensure that I can anticipate repetitive patterns earlier and avoid redundancy from the start.

What challenges did you encounter, and how did you overcome them?

One of the challenges I faced was managing space between elements, especially when it came to the end of a list or array. I initially had trouble with the layout not appearing properly because of the lack of space at the end of containers. To overcome this, I paid closer attention to the CSS margins and padding settings and tested them with different element sizes to ensure the design was responsive and visually balanced.

Another challenge was figuring out how to store and work with dynamic data inside a loop. I needed to store the last clicked button in a variable to manipulate it later. I overcame this by using a forEach loop to go through all the buttons, setting up event listeners, and storing the clicked button in a variable like selectedButton. This allowed me to keep track of the user’s interactions.

What specific areas of your project would you like help with?

I’m interested in getting feedback on how I can improve my implementation of the interactive rating component, particularly with spacing and alignment. Specifically, I would appreciate suggestions on how to manage space between elements dynamically, especially when elements are added or removed.

Additionally, I would love to improve the efficiency of storing and updating data in dynamic loops. Right now, I use simple variables like selectedButton, but I feel like there might be a more scalable way to handle multiple data points at once, especially when scaling up the number of interactive components. Any suggestions or best practices on this would be helpful!