| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Permissions, regex filters, app title, email info,
and safety now fetched using server's Info API
|
|
* Users are only authenticated against their password on login,
and to retrieve a token
* Passwords are wiped from the GUI frontend and cookies
after login and token retrieval
* Tokens are revoked at the end of the session/logout
* If the user chooses the "remember me" option,
the token is stored in the cookie
* Tokens correctly delete themselves on logout
* Tokens can expire at user-specified date
* Tokens have their last usage time
* Tokens can have user defined descriptions
* Users can manage login tokens in their account settings
|
|
Print all links through new uri.js component
Refactor the router to use more predictable parsing
Fix linking to entities with weird names (that contain slashes, + etc.)
|
|
|
|
User controller didn't need intervention but I refactored it to match
tag controller anyway.
|
|
In other words, verify the privileges client-side before issuing an
request to the server. This commit focuses on routing (e.g. clicking a
link while not logged in), rather than DOM element visibility that
should be already taken care of.
|
|
|
|
1. "change" should be used to passive changes.
2. "submit" should be used to form submits.
These are not interchangeable.
|
|
|
|
|
|
|
|
|
|
- Controller lifetime is bound to route lifetime
- View lifetime is bound to controller lifetime
- Control lifetime is bound to view lifetime
- Enhanced event dispatching
- Enhanced responsiveness in some places
- Views communicate user input to controllers via new event system
|
