aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application
Commit message (Collapse)AuthorAgeFilesLines
...
* Added ability to set asset_path for enginesPiotr Sarnacki2010-09-031-0/+15
|
* Ensure that Rails.application.initialize! is called only oncePiotr Sarnacki2010-09-031-0/+5
|
* Move singleton pattern to Railtie and remove Engine::Configurable and ↵Piotr Sarnacki2010-09-031-7/+6
| | | | Application::Configurable in favor of unified Railtie::Configurable
* Removed most of deprecated stuff from Application and EnginePiotr Sarnacki2010-09-031-16/+0
|
* Allow Engines loading its own environment file from config/environmentsPiotr Sarnacki2010-09-031-0/+17
|
* Remove deprecated dispatch test.José Valim2010-09-021-7/+0
|
* Ensure routes are loaded only after the initialization process finishes, ↵José Valim2010-09-021-0/+17
| | | | ensuring all configuration options were applied.
* Revert "Just add connection management middleware if running in a concurrent ↵Jeremy Kemper2010-08-202-11/+2
| | | | | | environment." This reverts commit 6b29dc876fe185881d46731c3ae170478a3828fe.
* Make sure apps upgrading from 2.3 get defaulted to UTF-8 (ht: parndt)wycats2010-08-151-5/+15
|
* Deletes trailing whitespaces (over text files only find * -type f -exec sed ↵Santiago Pastorino2010-08-142-4/+4
| | | | 's/[ \t]*$//' -i {} \;)
* Improve best_standards_support to use only IE=Edge in development modewycats2010-08-091-31/+65
|
* Fix middleware testwycats2010-07-271-1/+2
|
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-0/+1
| | | | | | available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin. This guarantees that the best available standards support will be used on the client.
* application generation: --skip-testunit and --skip-activerecord renamed to ↵Xavier Noria2010-07-251-1/+1
| | | | | | | | --skip-test-unit and --skip-active-record respectively Reason is their proper spellings are "Test::Unit" and "Active Record". Option names and descriptions have been revised, as well as some method names and minor details here and there.
* Make config.generators accept string namespaces, you can do now ↵Santiago Pastorino2010-07-211-0/+15
| | | | | | config.generators.test_framework 'rspec' for instance Signed-off-by: José Valim <jose.valim@gmail.com>
* Fix a failing test in Railtie and properly define all severity levels in ↵José Valim2010-07-201-14/+5
| | | | MockLogger for LogSubscriber.
* Add console hook to force ActiveRecord::Base to be loaded when console ↵José Valim2010-07-181-3/+18
| | | | starts avoiding reference loops.
* Just add connection management middleware if running in a concurrent ↵José Valim2010-07-122-2/+11
| | | | environment.
* Add a test to ensure url helpers are not action methods in ActionMailer.José Valim2010-07-071-0/+19
|
* Fix indentJeremy Kemper2010-07-021-1/+1
|
* Avoid calls to Rails::Application since this is not the official API.José Valim2010-07-013-4/+4
| | | | Your application should *always* reference your application const (as Blog::Application) and Rails.application should be used just internally.
* Create a deprecation behavior that triggers a notification for deprecation ↵wycats2010-06-291-0/+1
| | | | | | | | | | | | | | | | | notices, and make the behaviors independent of the environment names. * In Rails 2.3 apps being upgraded, you will need to add the deprecation configuration to each of your environments. Failing to do so will result in the same behavior as Rails 2.3, but with an outputted warning to provide information on how to set up the setting. * New Rails 3 applications generate the setting * The notification style will send deprecation notices using ActiveSupport::Notifications. Third-party tools can listen in to these notifications to provide a streamlined view of the deprecation notices occurring in your app. * The payload in the notification is the deprecation warning itself as well as the callstack from the point that triggered the notification.
* Push a failing test for issues [#4994] and [#5003].José Valim2010-06-291-1/+14
|
* adding missing assertion and fixing the testNeeraj Singh2010-06-241-2/+4
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* fixing test by replacing assert with assert_equalNeeraj Singh2010-06-241-1/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* adding middleware test for RAILS_CACHENeeraj Singh2010-06-241-0/+11
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Array#sample now exists, so test for #forty_two insteadJeremy Kemper2010-06-241-1/+1
|
* Added 4 tests for Rails Runner. 2 failing tests for $0 and $PROGRAM_NAME ↵rohit2010-06-221-0/+49
| | | | | | [#2244 state:open] Signed-off-by: José Valim <jose.valim@gmail.com>
* Revert "files in the lib directory are no longer autoloaded"Xavier Noria2010-06-211-3/+1
| | | | | | | This patch is not consistent since it leaves similar directories in load_paths, needs more thought. This reverts commit b5fe014fdcc285f3bcb8779c4f7cfbc5a820856f.
* files in the lib directory are no longer autoloadedXavier Noria2010-06-211-1/+3
| | | | | | | | | | | Conceptually, the lib directory is closer 3rd party libraries than to the application itself. Thus, Rails adds it to Ruby's load path ($LOAD_PATH, $:) but it is no longer included in dependencies' load paths. To enable autoloading back put this in your config/application.rb config.load_paths += %W( #{config.root}/lib )
* I18n.reload! is only called if any of the locale files actually changed.José Valim2010-06-201-19/+114
|
* Clear DescendantsTracker on each request.José Valim2010-06-194-35/+75
|
* Add a failing test for ticket #4874José Valim2010-06-171-0/+14
|
* edit pass: the names of Rails components have a space, ie, "Active Record", ↵Xavier Noria2010-06-141-1/+1
| | | | not "ActiveRecord"
* abort generation/booting on Ruby 1.9.1Xavier Noria2010-06-101-1/+3
|
* Ensure show exceptions middleware properly filters backtrace before logging.José Valim2010-06-091-0/+20
|
* Should call configure! to initiliaze the applicationSantiago Pastorino2010-06-091-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Add delete to middleware stack proxy.José Valim2010-06-071-0/+6
|
* removes Array#random_element and backports Array#sample from Ruby 1.9, ↵Xavier Noria2010-06-051-2/+2
| | | | thanks to Marc-Andre Lafortune
* Add lib to load paths when application is inherited to be able to load lib ↵José Valim2010-06-021-0/+17
| | | | code during configuration.
* Remove the laziness from the middleware stack.José Valim2010-05-291-1/+1
|
* Removing Metal from Rails 3. wycats2010-05-293-94/+0
| | | | | | | | | | | | | | | | | | | | If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
* Fix typo on rackup test (ht: pleax)José Valim2010-05-201-1/+1
|
* Final iteration of use better testing methodsNeeraj Singh2010-05-191-2/+2
| | | | | | [#4652 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Simplify cookie_store by simply relying on cookies.signed.José Valim2010-05-182-3/+6
|
* Renames Array#rand -> Array#random_elementRizwan Reza2010-05-171-2/+2
| | | | Signed-off-by: Xavier Noria <fxn@hashref.com>
* Revert "Moved encoding work in progress to a feature branch."wycats2010-05-171-1/+2
| | | | This reverts commit ade756fe42423033bae8e5aea8f58782f7a6c517.
* Moved encoding work in progress to a feature branch.Jeremy Kemper2010-05-161-2/+1
| | | | This reverts commits af0d1a88157942c6e6398dbf73891cff1e152405 and 64d109e3539ad600f58536d3ecabd2f87b67fd1c.
* Significantly improved internal encoding heuristics and support.wycats2010-05-161-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | * Default Encoding.default_internal to UTF-8 * Eliminated the use of file-wide magic comments to coerce code evaluated inside the file * Read templates as BINARY, use default_external or template-wide magic comments inside the Template to set the initial encoding * This means that template handlers in Ruby 1.9 will receive Strings encoded in default_internal (UTF-8 by default) * Create a better Exception for encoding issues, and use it when the template source has bytes that are not compatible with the specified encoding * Allow template handlers to opt-into handling BINARY. If they do so, they need to do some of their own manual encoding work * Added a "Configuration Gotchas" section to the intro Rails Guide instructing users to use UTF-8 for everything * Use config.encoding= in Ruby 1.8, and raise if a value that is an invalid $KCODE value is used Also: * Fixed a few tests that were assert() rather than assert_equal() and were caught by Minitest requiring a String for the message * Fixed a test where an assert_select was misformed, also caught by Minitest being more restrictive * Fixed a test where a Rack response was returning a String rather than an Enumerable
* Fixed two failing tests in railties on 1.9.2-head [#4609 state:commited]rohit2010-05-161-2/+2
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-07 22:25:00 +0000