Mon, Nov 25
Mon, Nov 18
Sat, Nov 16
Mon, Nov 11
Sep 24 2019
gist is, you've got a plane with 100 passengers, each assigned a seat. The first passenger to board is drunk and chooses a random seat assignment. Each subsequent passenger to board will choose his or her own seat if it is available, or a random seat if not. What is the probability that the final passenger to board will remain in his or her assigned seat?
Sep 8 2019
Sep 7 2019
Sep 1 2019
Aug 19 2019
Aug 18 2019
- address code review issues
- fix lint issues
- make it work after rebasing
My rough plan following this diff is basically:
- Switch up how we're doing page rendering since that's kind of murky current in terms of how we distinguish between 'build a sanitized HTML element' and 'render a specific page'. That can be cleaned up pretty easily and it's probably best to do that now while the codebase is still small
- Build out the UI for the initial user registration flow. I think this will be the same deal as for a generic user registration, just with a 'this user is an admin' flag toggled
- Build out some infrastructure around password management and credential checking. This'll be a "fun" learning adventure for me.
- Build out the ORM piece so we can actually register a user and store their info to the database
This implementation is also wrong atm. Properly, I'll need to use some flask wrapper function for this since __init__ by definition can't actually return anything (the implication being that, short of raising an exception, we can't interrupt the normal course of action and say, "Return page Y instead of page X"). I'll fix this in a subsequent diff.
Redirect to the appropriate registration route
Super basic check to see if at least 1 admin account has been registered yet
I will move things from view to route.
I will update the UI items including
- style header
- style button
- combine tables
- replace index with headers
So I think that for now we might want to keep the view and route folders separate, where view is more or less "How do we bring together all of the UI components on the page" and route is "What Python gets run when we go to a URL". It looks like you have all of the blueprint routing in view currently.
Aug 17 2019
Aug 14 2019
Aug 12 2019
Address review feedback
Aug 11 2019
Updates after rebasing
- Properly handle nested arguments
- fix style issues
- fix lint issues
Aug 9 2019
Aug 8 2019
Whoops! Sorry, almost forgot: mind fixing the PEP lint issues also?
- update codes based on review feedbacks