aboutsummaryrefslogtreecommitdiffstats
path: root/guides/bug_report_templates/action_controller_gem.rb
Commit message (Collapse)AuthorAgeFilesLines
* Replaced render :text with render :plain in AC gem bug report templatePrathamesh Sonpatki2015-07-181-1/+1
| | | | | - Followup of https://github.com/rails/rails/pull/20929. [ci skip]
* Output an error message and raise an error if bundler 1.10.x is not ↵akihiro172015-06-061-1/+6
| | | | installed when reporting bugs
* Add the bug report templates to the Travis CI buildRoque Pinel2015-06-051-3/+7
| | | | | | | | | | | | The bug report templates are now executed from the `ci/travis.rb` when `GEM` contains `guides`. I started by creating a `test` task in `guides/Rakefile` to handle this, but since inline `gemfile` must not be executed with `bundle exec`, that rake task would not be consistent with others. So I went back by executing them directly from `Build`. Use inline Gemfile dependency when reporting gem bugs
* load "rack/test" before "action_controller/railtie" in bug report templates ↵yuuji.yaginuma2015-02-051-1/+1
| | | | [ci skip]
* Update bug report templates to use version 4.2.0 instead of 5.0.0 [ci skip]Prathamesh Sonpatki2015-01-041-1/+1
| | | | | | | | - Right now master is 5.0.0. Latest gem release is 4.2.0 for which we are accepting bug reports. So lets use it in bug report templates. - 5.0.0 is not installable as it's not available on Rubygems yet. So the gem bug templates are not usable without editing the version. Using 4.2.0 will make them usable again.
* Using Rails 5.0 in bug report templates [ci skip]Lucas Caton2015-01-021-1/+1
|
* `secret_token` is now saved in `Rails.application.secrets.secret_token`Benjamin Fleischer2014-11-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | - `secrets.secret_token` is now used in all places `config.secret_token` was - `secrets.secret_token`, when not present in `config/secrets.yml`, now falls back to the value of `config.secret_token` - when `secrets.secret_token` is set, it over-writes `config.secret_token` so they are the same (for backwards-compatibility) - Update docs to reference app.secrets in all places - Remove references to `config.secret_token`, `config.secret_key_base` - Warn that missing secret_key_base is deprecated - Add tests for secret_token, key_generator, and message_verifier - the legacy key generator is used with the message verifier when secrets.secret_key_base is blank and secret_token is set - app.key_generator raises when neither secrets.secret_key_base nor secret_token are set - app.env_config raises when neither secrets.secret_key_base nor secret_token are set - Add changelog Run focused tests via ruby -w -Itest test/application/configuration_test.rb -n '/secret_|key_/'
* Ensure backward compatibility between Minitest 5 and 4Robin Dupret2013-12-271-1/+4
| | | | | | | | Define Minitest::Test in case we are running the gist under Minitest 4 and avoid relying on MiniTest::Unit::TestCase to avoid displaying warning on version five. [ci skip]
* Minitest::Unit::TestCase is Minitest::Test [ci skip]Arun Agrawal2013-12-261-1/+1
|
* Change all `MiniTest` to `Minitest` since, `MiniTest` namespace has been ↵Vipul A M2013-12-181-1/+1
| | | | | | renamed to `Minitest` Ref: https://github.com/seattlerb/minitest/blob/master/History.txt
* Include URL helpers in TestController in bug report templatesRoman Kushnir2013-11-111-0/+2
| | | | | | [ci skip] Fixes #12848.
* Added bug report template for ActionControllerPaul Nikitochkin2013-08-211-0/+42
[ci skip]
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-05 13:49:10 +0000