Destroy!

August 3, 2015 07:46 UTC Team RubyGirls Quito [2015]Subscribe to this teams's activities

A good weekend for finishing implementing users:

  1. Users can now edit their information.
  2. Implemented authorization.
  3. Allowed app to show all users.
  4. Used and learnt about faker gem.
  5. Used 'wil_paginate' method.
  6. Allowed admin to delete users: the destroy action.
  7. Removed some duplicated code.
  8. Wrote a test for error messages and for flash.
  9. Found an issue on 'test/integration/userssignuptest.rb', as assertselect is now based on Nokogiri. See here: http://edgeguides.rubyonrails.org/42releasenotes.html#assert-select. Should warn the creator of the tutorial about this change.
  10. Learnt about flash.now.
  11. Learnt to use session method, cookies method and remember token.

---Tasks for tomorrow--
Allow password reset and account activation, access the virtual 'remembertoken', check LEAP code to see the implementation of users, start thinking about 1st task: require admin to activate account before signin (as an admin approve new users). Learning about account activation might help understand 1st task. This approach might also help in that: https://github.com/plataformatec/devise/wiki/How-To:-Require-admin-to-activate-account-before-sign_in, http://stackoverflow.com/questions/5958300/devise-and-user-registration-requiring-admin-approval, http://stackoverflow.com/questions/15329041/browser-based-new-user-approval-by-admin-in-rails-3-2-app-using-devise. Allow destroy without Javascript: http://railscasts.com/episodes/77-destroy-without-javascript.

Comments

You must be logged in to add a comment.