This updated pull request implements the enhancements specified in ticket #652
The changes include:
Revised the main challenge explanation to improve clarity
Introduced a bonus challenge
Updated the challenge codebase
Refined the solution to the challenge
This is outdated ⤵️
~Reasons for adjusting the solution~
~The solution deviates from the initial challenge template given to students, which can cause confusion.~
~- Function Naming Inconsistency: The challenge template instructs students to use a function named getUser for fetching data. The solution changes this to loadUser.~
~- Inconsistency in User Interaction and Data Fetching: The template for the challenge uses async and await directly in the event listener. The solution does not explicitly handle the asynchronous process.~
~Further suggestions~
~- Implement structured error handling to enhance the robustness of our application.~
~- Handle UI updates separately within the event listener, maintaining a clear separation of concerns.~
This updated pull request implements the enhancements specified in ticket #652
The changes include:
This is outdated ⤵️ ~Reasons for adjusting the solution~
~The solution deviates from the initial challenge template given to students, which can cause confusion.~
~- Function Naming Inconsistency: The challenge template instructs students to use a function named
getUserfor fetching data. The solution changes this toloadUser.~ ~- Inconsistency in User Interaction and Data Fetching: The template for the challenge usesasyncandawaitdirectly in the event listener. The solution does not explicitly handle the asynchronous process.~~Further suggestions~ ~- Implement structured error handling to enhance the robustness of our application.~ ~- Handle UI updates separately within the event listener, maintaining a clear separation of concerns.~