leap_web.git - [leap

Age	Commit message (Collapse)	Author
2012-12-09	first steps towards email aliases	Azul
	* unit tests draft * controller draft
2012-12-08	serve api version 1 in /1/	Azul
	Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-12-07	fixed signup and removed flash that was not getting displayed	Azul
	I also tried flash.keep(:notice) but that did not help - not sure how to keep the flash until the root url has rendered.
2012-12-07	adding a bunch of translation	Azul

2012-12-07	first stub at displaying success messages	Azul

2012-12-07	refactor: use seperate form for signup	Azul
	creating and editing users differ so much now it's not worth reusing the complex user_form_with for the signup.
2012-12-07	using normal requests for user updates except password	Azul
	password requires ajax for secure remote password to work
2012-12-07	refactored views to ease adding of email form	Azul

2012-12-06	forgot to add new partial	Azul

2012-12-06	seperated login and password changes in settings	Azul

2012-12-03	enable users to cancel their account	Azul

2012-12-03	enable admin to edit users	Azul

2012-11-28	admins can destroy users	Azul
	I changed the permissions a little to be more consistent. Now: * admins can edit users * users can destroy themselves. There's no ui for either of them but theoretically they could. Not sure this is what we want though.
2012-11-26	forgot the user partial	Azul

2012-11-26	basic typeahead and user querying working	Azul

2012-11-26	basic users index with typeahead search	Azul

2012-11-26	added admin menu and user index action	Azul

2012-11-26	simplified controller and adjusted tests	Azul
	Also added #assert_json_error to tests.
2012-11-26	minor: client side validations fixed + .json request	Azul

2012-11-26	basic changing of password and login working	Azul

2012-11-23	identify user by id so rerendering the form does not use new invalid login	Azul

2012-11-23	test editing user settings	Azul

2012-11-22	basic user edit form and actions	Azul

2012-11-22	fixed tests	Azul

2012-11-22	beautify login workflow	Azul
	* translating error messages * not caching login and password in js anymore * catching non responses
2012-11-22	using client side validations for login	Azul

2012-11-22	using the new srp.js api	Azul

2012-11-20	ui tweaks to the menu	Azul

2012-11-13	using client side validations during signup	Azul

2012-11-12	Merge branch 'develop' into feature-client-side-validations	Azul
	Conflicts: Gemfile.lock
2012-11-12	adding client side validations to the mix	Azul

2012-11-12	fixed signup bug and refactored a bit	Azul

2012-11-09	got integration test and login flow to work	Azul

2012-11-09	Merge branch 'develop' into feature-warden-srp	Azul
	Conflicts: users/app/assets/javascripts/srp
2012-11-09	merged srp master into json api branch	Azul

2012-11-06	undo accidentally reverted srp-js and ruby 1.9 debugger in gemfile	Azul

2012-11-06	first steps towards warden srp testing	Azul

2012-11-04	fixed functional tests	Azul

2012-11-04	stubbing current_user the warden way	Azul

2012-11-04	Merge branch 'develop' into feature-warden-srp	Azul
	Conflicts: Gemfile.lock users/app/controllers/application_controller.rb users/leap_web_users.gemspec
2012-11-04	using ruby-srp 0.1.4 - ruby 1.9.3 compatible	Azul

2012-10-31	Code to check administration (and ugly test display.) This includes example ↵	jessib
	config file.
2012-10-31	Merge branch 'develop' into feature-admin_users	jessib
	Conflicts: users/app/controllers/application_controller.rb users/app/models/user.rb
2012-10-31	Merge branch 'develop' of ssh://leap.se/leap_web into develop	jessib

2012-10-31	using controller extensions for application controller by hand	Azul

2012-10-31	user creation should send ok flag so js can start login	Azul

2012-10-31	using json template for rendering the warden failures	Azul

2012-10-31	user creation should send ok flag so js can start login	Azul

2012-10-30	sending proper error messages from warden.	Azul
	still need to translate these
2012-10-30	using rails_warden bit of refactoring	Azul
	without rails_warden the failure app action was not getting set properly.