more woring improvements to the engines guide
* "also in ... is ..." -> "in .. there is ..." * use "as well" instead of "also" in the end of the sentence * "has the ability" -> "can"
This commit is contained in:
parent
a8d4e2788b
commit
1907409596
@ -171,7 +171,7 @@ end
|
||||
|
||||
This line mounts the engine at the path `/blorgh`, which will make it accessible through the application only at that path.
|
||||
|
||||
Also in the test directory is the `test/integration` directory, where integration tests for the engine should be placed. Other directories can be created in the `test` directory also. For example, you may wish to create a `test/models` directory for your models tests.
|
||||
In the test directory there is the `test/integration` directory, where integration tests for the engine should be placed. Other directories can be created in the `test` directory as well. For example, you may wish to create a `test/models` directory for your models tests.
|
||||
|
||||
Providing engine functionality
|
||||
------------------------------
|
||||
@ -288,7 +288,7 @@ Now people will only need to go to the root of the engine to see all the posts,
|
||||
|
||||
### Generating a comments resource
|
||||
|
||||
Now that the engine has the ability to create new blog posts, it only makes sense to add commenting functionality as well. To do get this, you'll need to generate a comment model, a comment controller and then modify the posts scaffold to display comments and allow people to create new ones.
|
||||
Now that the engine can to create new blog posts, it only makes sense to add commenting functionality as well. To do get this, you'll need to generate a comment model, a comment controller and then modify the posts scaffold to display comments and allow people to create new ones.
|
||||
|
||||
Run the model generator and tell it to generate a `Comment` model, with the related table having two columns: a `post_id` integer and `text` text column.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user