Skip to content

Commit

Permalink
update generation instructions for consistency
Browse files Browse the repository at this point in the history
New to Rails but looks like everything for an engine should be done inside the engine's folder. The updated text has been there for a long time so I hope I'm not just missing something. At this point in the example the user does not have an application (that comes in the next section) and elsewhere in the doc there is talk of the importance of running the commands from the *engine* root so it seems more consistent to talk about "engine root" as updated.
  • Loading branch information
jeffmcaffer committed Aug 18, 2020
1 parent 161fc87 commit d27a2a9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions guides/source/engines.md
Expand Up @@ -465,7 +465,7 @@ commenting functionality as well. To do this, you'll need to generate a comment
model, a comment controller, and then modify the articles scaffold to display
comments and allow people to create new ones.

From the application root, run the model generator. Tell it to generate a
From the engine root, run the model generator. Tell it to generate a
`Comment` model, with the related table having two columns: an `article_id` integer
and `text` text column.

Expand Down Expand Up @@ -561,7 +561,7 @@ end
This creates a nested route for the comments, which is what the form requires.

The route now exists, but the controller that this route goes to does not. To
create it, run this command from the application root:
create it, run this command from the engine root:

```bash
$ bin/rails generate controller comments
Expand Down

0 comments on commit d27a2a9

Please sign in to comment.