1
0
Fork 0
mirror of https://github.com/heartcombo/devise.git synced 2022-11-09 12:18:31 -05:00
heartcombo--devise/lib/devise
2009-12-20 12:31:02 +01:00
..
controllers Copy and paste from skype is not as good as it sounds. Removing invisible/odd/strange characters which make Devise fail with Ruby 1.9. 2009-12-19 20:32:32 +01:00
encryptors Tidying up encryptors. 2009-11-10 18:55:13 -02:00
hooks Added trackable for sign_in_count, sign_in_at and sign_in_ip. 2009-11-24 15:18:42 -02:00
locales Adding i18n flash message when session is expired. 2009-11-23 23:01:01 -02:00
models Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable. 2009-12-20 12:31:02 +01:00
orm More Datamapper compatibility. 2009-11-24 18:02:36 -02:00
rails Remove deprecation warning, extract SessionSerializer and release new version. 2009-12-07 21:00:44 -02:00
serializers Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable. 2009-12-20 12:31:02 +01:00
strategies Improve more loading process. 2009-12-07 20:26:00 -02:00
failure_app.rb Allow a strategy to be added after authenticatable one and move store_location to FailureApp. 2009-11-22 00:49:23 -02:00
mapping.rb More tweaks for plugin compatibility. 2009-12-08 20:39:38 -02:00
models.rb Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable. 2009-12-20 12:31:02 +01:00
rails.rb Rely on Warden new serializers. 2009-11-15 00:13:43 -02:00
schema.rb Do not check class collisions, we want to be able to scaffold and then apply Devise on top of it. 2009-12-15 00:07:42 +01:00
test_helpers.rb Allow to sign in with two different users in the same functional test with Devise::TestHelpers. 2009-12-14 22:48:15 +01:00
version.rb Release Devise 0.7.3. 2009-12-16 01:29:19 +01:00