-
Szymon Kurcab authored
* Add context argument for an authenticator to use Sometimes a login might require more information than just a username and password, in these cases the extra info can be pased to the authenticator via the context parameter as a Hash. * Created configurable authenticator context * Don't assume the context is a `Hash` * Added CHANGELOG.md * Fix deprecations and settings for Rails 4.2 * Fix test that never should have worked - failed after fixing deprecations * Add testing for Ruby 2.4.0 and 2.4.1 * Rubocop cleanup * FactoryGirl is deprecated and replaced with FactoryBot (renamed) * Loosen gem versioning * Ran `bundle exec rake rails:update` to upgrade to Rails 4.2 settings * Version bump v4.2.0 * Updated CHANGELOG for v4.2.0 * Implemented Appraisal tests for Rails 4.2, 5.0, and 5.1 * Don't explicitly set this option that is not available in Rails 5.x * Reference Rails Engine path (when mounted inside one) * Copy migrations with a generator because `rake casino:install:migrations` doesn't work from Rails Engine * Simplified adding namespace to paths * Rails 5.0 deprecations fixed * Add extracted gem to fix failing tests * Updated lambda stynax * Use `all` scope for scope chaining instead of class * Updated RSpec version for specific Rails versions * Remove version constraint to allow for Rails 5.x * Add ApplicationRecord base class for models * Add migration version to migrations * Use `data_source_exists?` to check for tables and views - gets rid of deprecation warning that `table_exists?` will only check tables in Rails 5.1 * Set new option explicitly * Fix deprecated queries for Rails 5.0 * Use keyword arguments in integration tests for Rails 5.0 * Fixing check for empty params - IntegrationTest converts `nil` params to blank strings: https://github.com/rails/rails/issues/28129 * Call `super` without implicit arguments * Invert logic * Fix checks to look for blank values instead of `nil` to address IntegrationTest change AND potential security issues * Explicitly respond with 406 status because this changed in Rails 5.0 - https://github.com/rails/rails/issues/20666 * Drop Rails 4.2 support - mainly because of keyword arguments in RSpec integration tests * Version bump v5.0.0 (Rails 5.0+ support) * Remove Rails 4.2 tests * Allow Ruby 2.4.x failures * Consolidate logic * Updated CHANGELOG
Szymon Kurcab authored* Add context argument for an authenticator to use Sometimes a login might require more information than just a username and password, in these cases the extra info can be pased to the authenticator via the context parameter as a Hash. * Created configurable authenticator context * Don't assume the context is a `Hash` * Added CHANGELOG.md * Fix deprecations and settings for Rails 4.2 * Fix test that never should have worked - failed after fixing deprecations * Add testing for Ruby 2.4.0 and 2.4.1 * Rubocop cleanup * FactoryGirl is deprecated and replaced with FactoryBot (renamed) * Loosen gem versioning * Ran `bundle exec rake rails:update` to upgrade to Rails 4.2 settings * Version bump v4.2.0 * Updated CHANGELOG for v4.2.0 * Implemented Appraisal tests for Rails 4.2, 5.0, and 5.1 * Don't explicitly set this option that is not available in Rails 5.x * Reference Rails Engine path (when mounted inside one) * Copy migrations with a generator because `rake casino:install:migrations` doesn't work from Rails Engine * Simplified adding namespace to paths * Rails 5.0 deprecations fixed * Add extracted gem to fix failing tests * Updated lambda stynax * Use `all` scope for scope chaining instead of class * Updated RSpec version for specific Rails versions * Remove version constraint to allow for Rails 5.x * Add ApplicationRecord base class for models * Add migration version to migrations * Use `data_source_exists?` to check for tables and views - gets rid of deprecation warning that `table_exists?` will only check tables in Rails 5.1 * Set new option explicitly * Fix deprecated queries for Rails 5.0 * Use keyword arguments in integration tests for Rails 5.0 * Fixing check for empty params - IntegrationTest converts `nil` params to blank strings: https://github.com/rails/rails/issues/28129 * Call `super` without implicit arguments * Invert logic * Fix checks to look for blank values instead of `nil` to address IntegrationTest change AND potential security issues * Explicitly respond with 406 status because this changed in Rails 5.0 - https://github.com/rails/rails/issues/20666 * Drop Rails 4.2 support - mainly because of keyword arguments in RSpec integration tests * Version bump v5.0.0 (Rails 5.0+ support) * Remove Rails 4.2 tests * Allow Ruby 2.4.x failures * Consolidate logic * Updated CHANGELOG
Loading