Profile Page

[andrewsosa]

This should display:

• [x] acceptance status
• [x] information from the application
• [x] hacker's QR code

[andrewsosa]

Should use /profile path.

~Attempting to access the profile page before all 3 segments of the application are complete should redirect a user back to the /register path. When redirecting, pass a URL parameter corresponding to the proper segment of the application.~

~For example, if the user goes to /profile:~

1. ~But doens't have an account (no User model), redirect them to the home page again.~
2. ~Has an account but no UserInfo model, direct them to part 2.~
3. ~Has a UserInfo model but no HackerInfo model, direct them to part 3.~
4. ~If everything is accounted for, display page data.~

~We need to discuss the right way to toggle parts of the /register page to hide already completed portions of the application.~

~Completing this behavior is more important than displaying items.~

Crossed out text irrelevant, registration took a different path.

[andrewsosa]

Delaying this until jan

[andrewsosa]

The hexcode is available at /api/user/get/profile/hexcode on the qr-service branch, which as of writing this isn't on any remote. But yeah, for future reference.

[andrewsosa]

We'll be introducing /api/user/get/profile/qr soon.

[andrewsosa]

Implemented in e05f1a82b9b8a7ebd1f3cd6555b002ee3eee0b5d