aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/engine
Commit message (Collapse)AuthorAgeFilesLines
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-15/+15
|
* removes usage of Object#in? from the code base (the method remains defined ↵Xavier Noria2012-08-061-3/+1
| | | | | | | | | | | | | | | | | | | by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
* Revert "Allow loading external route files from the router"José Valim2012-06-291-1/+0
| | | | | | | | | | | | | | This reverts commit 6acebb38bc0637bc05c19d87f8767f16ce79189b. Usage of this feature did not reveal any improvement in existing apps. Conflicts: actionpack/lib/action_dispatch/routing/mapper.rb guides/source/routing.textile railties/lib/rails/engine.rb railties/lib/rails/paths.rb railties/test/paths_test.rb
* Remove unnecessary Railties structure now that plugins are goneJosé Valim2012-06-291-26/+0
|
* Revert "require the constants we use. ensure that root always returns a ↵Aaron Patterson2012-05-231-2/+1
| | | | | | Pathname" This reverts commit d77b576c0330d8b1c6189cb94814382ce32baab6.
* require the constants we use. ensure that root always returns a PathnameAaron Patterson2012-05-231-1/+2
|
* Merge pull request #3359 from mrreynolds/datamapper_naming_fixRafael Mendonça França2012-05-191-1/+1
|\ | | | | Fixed DataMapper namings in symbols and constants.
| * Fixed DataMapper namings in symbols and constants.Robert Glaser2011-10-181-1/+1
| |
* | Give more detailed instructions in script/rails in enginePiotr Sarnacki2012-05-041-0/+4
| | | | | | | | closes #4894
* | Make files in paths consistentYehuda Katz2012-04-251-1/+1
| |
* | Allow loading external route files from the routerJose and Yehuda2012-04-251-1/+2
| | | | | | | | | | | | | | | | | | This feature enables the ability to load an external routes file from the router via: draw :filename External routes files go in +config/routes+. This feature works in both engines and applications.
* | Rails::Plugin has goneSantiago Pastorino2012-01-032-10/+1
| |
* | fix nodocsVijay Dev2011-12-091-1/+1
|/
* Add destroy alias to enginesGuillermo Iguaran2011-08-221-2/+3
|
* Use namespace if it's a mountable engineStefan Sprenger2011-06-071-0/+1
|
* Add destroy to engine's commandsStefan Sprenger2011-05-271-2/+3
|
* Move requiring engine out of the switch caseStefan Sprenger2011-05-271-4/+3
|
* Introducing engine commandsStefan Sprenger2011-05-261-0/+37
|
* Need it declared tooDavid Heinemeier Hansson2011-05-101-0/+1
|
* Remove the ability for engines to serve assets from the public directory.José Valim2011-04-151-8/+1
|
* Booya, sprockets now works from Engines.José Valim2011-04-151-0/+2
|
* Rails::Engine.find(path) - method to find engine by pathPiotr Sarnacki2010-12-091-0/+10
|
* Make deep copy of application generators on engine initialization.Piotr Sarnacki2010-11-021-1/+1
| | | | | Otherwise nested hashes will be same objects for both application and engine, which will result in overwriting each others values on changes.
* Use application's generators defaults as engine defaults to not force users ↵Piotr Sarnacki2010-11-021-0/+1
| | | | to manually set it
* Provide a cleaner syntax for paths configuration that does not rely on ↵José Valim2010-10-062-23/+22
| | | | method_missing.
* Deprecate generators in Railties. You should use app_generators instead.José Valim2010-10-021-3/+25
|
* Add helper for loading seed data for engine and applicationPiotr Sarnacki2010-09-201-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Include all helpers from non-namespaced enginesPiotr Sarnacki2010-09-031-0/+1
|
* Get rid of static_paths method and instead configure paths for ↵Piotr Sarnacki2010-09-031-0/+4
| | | | ActionDispatch::Static in initializers
* Added Rails.application.config.paths.db.migrate to remove hardcoded ↵Piotr Sarnacki2010-09-031-0/+2
| | | | db/migrate paths
* Added ability to set asset_path for enginesPiotr Sarnacki2010-09-031-1/+1
|
* Move singleton pattern to Railtie and remove Engine::Configurable and ↵Piotr Sarnacki2010-09-031-31/+0
| | | | Application::Configurable in favor of unified Railtie::Configurable
* Allow Engines loading its own environment file from config/environmentsPiotr Sarnacki2010-09-031-0/+1
|
* Removed ActionDispatch::Static, but left empty MiddlewareStack to unify app ↵Piotr Sarnacki2010-09-032-7/+1
| | | | method between Engine and Application
* Engine can now serve files with ActionDispatch::StaticPiotr Sarnacki2010-09-031-2/+3
|
* Engine can now load its own pluginsPiotr Sarnacki2010-09-032-1/+26
|
* Made Engine valid rack app with its own middleware stackPiotr Sarnacki2010-09-032-1/+14
|
* Revert "Put lib back on the autoload path"José Valim2010-08-041-1/+1
| | | | | | This was causing engines/gems to eager load everything in lib. Another fix is comming soon. This reverts commit 02a5842cd09bd75de4c2fdb6b474c6c0ff163ebf.
* Put lib back on the autoload pathwycats2010-08-031-1/+1
|
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-1/+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.
* A few changes were done in this commit:José Valim2010-06-281-2/+2
| | | | | | * Added :autoload to engines path API and redefine usage to be in sync with 6f83a5036d8a9c3f8ed7; * Do not autoload code in *lib* for applications (now you need to explicitly require them). This makes an application behave closer to an engine (code in lib is still autoloaded for plugins); * Always autoload code in app/ for engines and plugins. This makes engines behave closer to an application and should allow us to get rid of the unloadable hack required when controllers inside engines inherit from ApplicationController;
* renames load_(once_)paths to autoload_(once_)paths in dependencies and configXavier Noria2010-06-241-5/+5
|
* Revert "files in the lib directory are no longer autoloaded"Xavier Noria2010-06-211-5/+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/+5
| | | | | | | | | | | 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 )
* Removing Metal from Rails 3. wycats2010-05-291-1/+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 a typo in load_once_paths [#4357 state:resolved] (ht: Kim Altintop)José Valim2010-04-101-1/+1
|
* Remove app/views from the load paths [#4226 state:resolved]José Valim2010-04-051-1/+1
|
* Rename config.cookie_secret to config.secret_token and pass it as ↵José Valim2010-04-051-1/+0
| | | | configuration in request.env. This is another step forward removing global configuration.
* Add mailers to paths in case someone wants to access it directly and ensures ↵José Valim2010-03-061-2/+3
| | | | deep nesting works in controllers.
* Deprecated ActionController::Base.session_options= and ↵Carlhuda2010-03-041-0/+1
| | | | ActionController::Base.session_store= in favor of a config.session_store method (which takes params) and a config.cookie_secret variable, which is used in various secret scenarios. The old AC::Base options will continue to work with deprecation warnings.
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 06:55:40 +0000