P
@CHBNDJSubmitted 4 months ago
What are you most proud of, and what would you do differently next time?
None
What challenges did you encounter, and how did you overcome them?None
What specific areas of your project would you like help with?None
Latest comments
- @AndresLamarPosted 4 months ago
Hey, hope you´re doing well, i encounter some problems in your solution:
- The buttons functionality trigger when clicking only in the SVG, it should trigger when clicking in the button itself.
- Only change the image, but no the text.
0 - @pgsousa10Submitted about 1 year ago
- @Sandaruwan7056Submitted 4 months agoWhat are you most proud of, and what would you do differently next time?
"I’ve learned how to use BEM and plan to improve my BEM structure as I continue learning."
What specific areas of your project would you like help with?nothing in particular any tips will be helpful
@AndresLamarPosted 4 months agoGreat solution, very accurate, the only thing that is missing are the active states for title and name of author.
0 - P@NikitaVologdinSubmitted 5 months ago@AndresLamarPosted 5 months ago
Excellent solution! Maybe in this project there was no need to use React-router, in the live site when clicking in any nav page it redirects to a empty page with 404, that's no a good user experience.
Marked as helpful0 - @Et18nSubmitted 8 months ago@AndresLamarPosted 5 months ago
Great solution, you should add an anchor tag to elements that are supposed to be navigables, like the navbar items or the articles in the aside section.
Marked as helpful0 - @Mubarak-AdeyemiSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
I’m most proud of implementing real-time validation with accessible error messages, which improves usability for screen readers and provides immediate feedback for users. If I could do it again, I’d focus more on refining error-handling logic and exploring more advanced accessibility techniques, like dynamic ARIA live regions for validation updates.
What challenges did you encounter, and how did you overcome them?- One of the main challenges was properly validating and updating the appearance of radio buttons when checked. Initially, I mistakenly used .forEach() instead of .some(), which complicated validation checks. The aim was to validate the selection and change the background colour of the selected radio label efficiently. iIcorporating .some() allowed me to more easily determine if at least one radio button was selected, simplifying the validation logic.
Debugging the radio button styling was another hurdle. I needed to ensure the correct background colour appeared only when a button was selected, removing the style if unchecked. By creating functions to manage background and border changes, I achieved a cleaner, dynamic approach that adapted to the user's interactions.
- The first solution led me to this challenge of the handleQueryType (or validateQueryType) function, which was returning undefined due to the use of the .forEach() method. Because .forEach() does not return a value, I couldn’t easily check if any radio button was selected.
To fix this, I refactored the function to use Array.from().some() only, allowing me to check if any radio button was selected. This way, the function returned true if at least one radio was checked and false otherwise, making the validation logic much simpler and more reliable. This approach enhanced both the accuracy and readability of the validation process.
@AndresLamarPosted 5 months agoGreat solution, i encounter some bugs when using the autocomplete in First and Last name inputs, if i use autocomplete it appears the error of invalid input, and you also should verify the space of the error messages, because some errors overlap the label that is below it.
0
