leap_web.git - [leap

Age	Commit message (Collapse)	Author
2013-07-24	separate signup and settings service objects for user	Azul

2013-07-24	setter for keys for dirty tracking, more robust tests	Azul
	Just altering identity.keys did not mark identities as changed. Also we now have a sane default for keys.
2013-07-24	no need for a remote email class	Azul

2013-07-24	support deprecated API to set users main identity pgp key	Azul
	We'll want to get rid of the #public_key and #public_key= functions but they are still used from the users controller. We'll probably have an identity controller instead at some point.
2013-07-24	add keys to identity	Azul

2013-07-24	remove the remainders of email aliases and forward from user	Azul

2013-07-24	allow available and unique forwards only	Azul

2013-07-24	validations of email format and local domain moved over	Azul

2013-07-24	local email adds domain if needed	Azul

2013-07-24	testing all versions of emial identities, emails are now strings	Azul

2013-07-24	move identity creation into user class	Azul
	It's always based on a user and most default values are based on user properties.
2013-07-24	first take on identity model - still broken	Azul

2013-07-16	prevent _ prefixes for couchDB document ids	Azul

2013-07-08	Merge branch 'master' into feature/disable_account	jessib
	Conflicts: users/app/controllers/users_controller.rb users/app/helpers/users_helper.rb users/app/views/users/edit.html.haml users/app/views/users/show.html.haml users/config/locales/en.yml
2013-07-04	allow forms with blank email forward.	elijah

2013-07-03	Accounts can be enabled or not. Admins can edit this property.	jessib

2013-04-25	Merge pull request #40 from azul/feature/token-auth	jessib
	Token auth with a database of it's own
2013-04-24	renamed and fixed pgp_key view	Azul

2013-04-09	let's use safe ids instead of the default couch ones	Azul
	Couch uses partly random partly sequential ids by default. We could change that in couch config to be all random. But this is probably more safe.
2013-04-09	initial token model and unit test	Azul

2013-04-03	make sure user tests also run when run from users subdir	Azul
	* The APP_CONFIG needs to be initialized in core so that is required from other engines * paths for load_views need to be relative to the model - not to rails root.
2013-02-28	Have specific error messages for usernames with incorrect formats.	jessib
	Signed-off-by: jessib <jessib@leap.se>
2013-02-26	Changes to valid format for usernames.	jessib

2013-02-06	using ruby-srp 0.1.5 SRP::Client to wrap user in session	Azul

2013-01-22	Rough way to allow user to paste in their key, but certainly we will want ↵	jessib
	different display.
2013-01-22	some basic webfinger routes, controller, presenters, views	Azul

2013-01-18	more flexible email partial	Azul

2013-01-18	Merge remote-tracking branch 'origin/master' into feature/fixed-email-address	Azul
	Conflicts: users/app/views/emails/_email.html.haml
2013-01-17	minor fixes to validation workflow	Azul

2013-01-17	unit tests passing	Azul

2013-01-16	incomplete initial changes to make email address just login@domain.tld	Azul
	This involves a number of other changes like making sure the comparison between aliases and emails still works. Will do that by removing the @domain.tld from aliases as well.
2013-01-14	Use partials for displaying details shown when viewing a user. Some of these ↵	jessib
	partials have specific CSS for another use, so we will likely want to tweak this.
2013-01-14	Merge branch 'master' into feature/show_user. Added new tests.	jessib
	Conflicts: users/test/functional/users_controller_test.rb
2013-01-14	got users controller test to pass - tickets controller test next.	Azul

2013-01-11	basic dummy data for users	Azul

2013-01-08	Adding show view for users.	jessib

2012-12-22	moving the js for view definitions into separate files	Azul
	This way we get syntax highlighting and so on.
2012-12-20	fixed tests, testing corner cases, fixed these	Azul

2012-12-20	this is what += is there for	Azul

2012-12-20	validating email domain and displaying it as the placeholder	Azul
	This even works client side. :)
2012-12-18	make sure we have email_aliases at all before testing for an error on the last	Azul

2012-12-18	refactored email_alias creation and validation	Azul
	using CouchRests user.email_aliases.build so the casted_by method is set in the alias Used this to move the validations into the alias itself. This is where they belong and allows us to render the errors inline along the email field they belong to.
2012-12-17	enabled destroying email aliases - no ajax yet.	Azul

2012-12-13	Merge branch 'feature/email-aliases-model'	Azul

2012-12-13	use the same partial for Email and LocalEmail	Azul

2012-12-13	refactor: changed add_email to add_email_alias	Azul
	that's what it does. Changed all tests to use it instead of the attributes method
2012-12-13	refactor: Email constructor now takes string or hash	Azul
	This allows us to reuse add_email from email_aliases_attributes=
2012-12-13	refactor: allow adding email aliases directly	Azul

2012-12-13	ensure users do not have duplicate email aliases	Azul
	nor aliases that are the same as the original email for that matter
2012-12-13	LocalEmail added - will validate uniqueness amongst emails and aliases	Azul