leap_web.git - [leap

Age	Commit message (Collapse)	Author
2014-01-07	Some refactoring, to simplify user model, optimize, and allow messages to be ↵	jessib
	sorted by date (although are not now.) Also, rather than use whenever gem, will have cron job created to call task.
2013-12-31	Cleanup of code for messages API and cron job for 1 month payment warning. ↵	jessib
	Authentication still remaining piece.
2013-12-30	Fixes to initial go at job to send one month warnings.	jessib

2013-12-30	Merge branch 'feature/messages_api' into feature/messages_cron	jessib

2013-12-30	Change structure to be more no-sql-y, rather than relational.	jessib

2013-12-30	Not actually how we want to do this, but at least finish outlined part, that ↵	jessib
	will later be replaced.
2013-12-26	Very very rough start to having messages for payment automatically created.	jessib

2013-12-24	Add API tests and some refactoring of messages so we can get a user's ↵	jessib
	messages within the webapp.
2013-12-03	Some simplification of code.	jessib

2013-12-03	Add ServiceLevel class to wrap config and give accessors. Has some hacky ↵	jessib
	parts, but seems like okay generic start for now.
2013-11-18	Start of service level code, which will be tweaked	jessib
	* stores desired & effective service level * whenever desired level is changed, effective level will be updated * allows user to set their desired service level * allow admin to update desired & effective service level
2013-09-18	user.account shortcut to Account.new(user)	Azul

2013-09-03	Account: Composition to handle User and its identities	Azul
	We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).
2013-08-30	there's no need for User#find_by_param. clean it up	Azul

2013-08-21	use the same login validations on sessions and users	Azul
	The session ones were outdated so valid usernames could not login if they contained a '.' Refactored so both models use the same module for this validation to ensure consistency.
2013-07-24	keeping the pgp_key accessors for User so views still work	Azul

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	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	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-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-24	renamed and fixed pgp_key view	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	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	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	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