An error occurred fetching the project authors.
- 27 Feb, 2019 1 commit
-
-
Tim Zallmann authored
EE Specific CSS Fixes Removed an extraneous whitespace Fixed single quotes in notes.scss
-
- 19 Oct, 2018 1 commit
-
-
Takuya Noguchi authored
Replaces .card-header > hX.card-title with hX.card-header to remove .card-title. At a occurrence where bold styling is not necessary, div.card-header is used instead. By full removal of .card-title at the moment, all workarounds for BS4's card-title are removed as well. More information: https://getbootstrap.com/docs/4.0/migration/#panelsSigned-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
-
- 04 Jun, 2018 1 commit
-
-
Tim Zallmann authored
-
- 09 May, 2018 1 commit
-
-
tauriedavis authored
-
- 07 May, 2018 1 commit
-
-
Bob Van Landuyt authored
-
- 04 May, 2018 7 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
This enforces the terms in the web application. These cases are specced: - Logging in: When terms are enforced, and a user logs in that has not accepted the terms, they are presented with the screen. They get directed to their customized root path afterwards. - Signing up: After signing up, the first screen the user is presented with the screen to accept the terms. After they accept they are directed to the dashboard. - While a session is active: - For a GET: The user will be directed to the terms page first, after they accept the terms, they will be directed to the page they were going to - For any other request: They are directed to the terms, after they accept the terms, they are directed back to the page they came from to retry the request. Any information entered would be persisted in localstorage and available on the page.
-
Bob Van Landuyt authored
When a user accepts, we store this in the agreements to keep track of which terms they accepted. We also update the flag on the user.
-
Bob Van Landuyt authored
When terms are present, they can be viewed on `/-/users/terms`.
-
Bob Van Landuyt authored
This enforces the terms in the web application. These cases are specced: - Logging in: When terms are enforced, and a user logs in that has not accepted the terms, they are presented with the screen. They get directed to their customized root path afterwards. - Signing up: After signing up, the first screen the user is presented with the screen to accept the terms. After they accept they are directed to the dashboard. - While a session is active: - For a GET: The user will be directed to the terms page first, after they accept the terms, they will be directed to the page they were going to - For any other request: They are directed to the terms, after they accept the terms, they are directed back to the page they came from to retry the request. Any information entered would be persisted in localstorage and available on the page.
-
Bob Van Landuyt authored
When a user accepts, we store this in the agreements to keep track of which terms they accepted. We also update the flag on the user.
-
Bob Van Landuyt authored
When terms are present, they can be viewed on `/-/users/terms`.
-