github/rails
1
1
Fork 0
mirror of https://github.com/github/rails.git synced 2026-04-26 03:00:59 -04:00
Code Issues Packages Projects Releases Wiki Activity

fixed a few filenames and paths

Browse Source
This commit is contained in:
Rich Sturim
2009-01-21 23:39:33 -05:00
parent f08a78a057
commit 74fd2d34f2
6 changed files with 10 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
railties/doc/guides/source/creating_plugins/creating_plugins/lib/main.rb Normal file
View File

@@ -0,0 +1,4 @@
# To change this template, choose Tools | Templates
# and open the template in the editor.
puts "Hello World"

2
railties/doc/guides/source/creating_plugins/generator_commands.txt
View File

@@ -120,7 +120,7 @@ Rails::Generator::Commands::List.send :include, Yaffle::Generator::Commands
Rails::Generator::Commands::Update.send :include, Yaffle::Generator::Commands::Update
-----------------------------------------------------------
*vendor/plugins/yaffle/generators/yaffle/yaffle_route_generator.rb*
*vendor/plugins/yaffle/generators/yaffle_route/yaffle_route_generator.rb*
[source, ruby]
-----------------------------------------------------------

23
railties/doc/guides/source/creating_plugins/migrations.txt
View File

@@ -28,26 +28,7 @@ Here are a few possibilities for how to allow developers to use your plugin migr
=== Create a custom rake task ===
*vendor/plugins/yaffle/lib/db/migrate/20081116181115_create_birdhouses.rb:*
[source, ruby]
----------------------------------------------
class CreateBirdhouses < ActiveRecord::Migration
def self.up
create_table :birdhouses, :force => true do |t|
t.string :name
t.timestamps
end
end
def self.down
drop_table :birdhouses
end
end
----------------------------------------------
*vendor/plugins/yaffle/tasks/yaffle.rake:*
*vendor/plugins/yaffle/tasks/yaffle_tasks.rake:*
[source, ruby]
----------------------------------------------
@@ -153,7 +134,7 @@ NOTE: the migration generator checks to see if a migation already exists, and it
After running the test with 'rake' you can make it pass with:
*vendor/plugins/yaffle/generators/yaffle/yaffle_generator.rb*
*vendor/plugins/yaffle/generators/yaffle_migration/yaffle_migration_generator.rb*
[source, ruby]
------------------------------------------------------------------

2
railties/doc/guides/source/creating_plugins/models.txt
View File

@@ -20,7 +20,7 @@ vendor/plugins/yaffle/
As always, start with a test:
*vendor/plugins/yaffle/yaffle/woodpecker_test.rb:*
*vendor/plugins/yaffle/test/woodpecker_test.rb:*
[source, ruby]
----------------------------------------------

4
railties/doc/guides/source/creating_plugins/tasks.txt
View File

@@ -1,10 +1,10 @@
== Rake tasks ==
When you created the plugin with the built-in rails generator, it generated a rake file for you in 'vendor/plugins/yaffle/tasks/yaffle.rake'. Any rake task you add here will be available to the app.
When you created the plugin with the built-in rails generator, it generated a rake file for you in 'vendor/plugins/yaffle/tasks/yaffle_tasks.rake'. Any rake task you add here will be available to the app.
Many plugin authors put all of their rake tasks into a common namespace that is the same as the plugin, like so:
*vendor/plugins/yaffle/tasks/yaffle.rake*
*vendor/plugins/yaffle/tasks/yaffle_tasks.rake*
[source, ruby]
---------------------------------------------------------

3
railties/doc/guides/source/creating_plugins/test_setup.txt
View File

@@ -116,9 +116,6 @@ ActiveRecord::Schema.define(:version => 0) do
t.string :last_tweet
t.datetime :last_tweeted_at
end
create_table :woodpeckers, :force => true do |t|
t.string :name
end
end
----------------------------------------------