Challenge Overview
Competition Task Overview
For this challenge, we need to update the QMS home screen based on the provided prototype and make some other UI / misc bug fixes.
Detailed Requirements
Here's what we need to do:
- Finish all changes mentioned in the requirements document and the other QMS | Flow Tweaks document (though most of the changes in this doc are done in the prototype so you'll just need to apply the UI to the app)
- Currently left / right arrow keys don't work once "Send link" is focused, we need to make sure this works as it does in the current code. The only issue with the current code is that when you use left key to navigate from Send link button it goes to the left most position of the digits and there's no way to delete the digits, so this issue needs to be fixed in this challenge as well.
- Up/ Down arrow keys currently work in the app but need to be disabled
- The phone number input needs to show "Enter a phone" when not focused (just like the current code), and show "--" when focused (like the prototype).
Code
- Please post in the forum to request to be added to the QMS gitlab team on gitlab if you are not already a member. Make sure you include your gitlab username in your post.
- Once added to the team, fork the repository, if you haven’t already, and work off of the challenge-30046967 branch.
- Add huangqun and lazybaer as members of your forked repository
Winner Responsibility
The winner will be asked to submit a merge request and help with merge if necessary. NO OTHER MEMBERS should submit a merge request since that reveals your code to everyone else.
Technology Overview
- Node.js
- Javascript
Final Submission Guidelines
Submission Deliverables
- Push your changes to your own private branch and make sure lazybear and huangqun have access to it so we can review
- Submit to online review once you've made the changes so we know we should review your changes. NOTE if you don't submit to online review there's no way we can accept your submission and pay you even if you are the first one to fix it.
Final Submission
For each member, the changes must be done to his/her own private branch, and then submit a file that includes revision number to online review to let us know the changes are ready for review.