Skip to content

Explain how route nesting works with an example #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2014
Merged

Explain how route nesting works with an example #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,18 @@ way down the view hierarchy. This allows you to create nested layouts
without having to wire it all up yourself. `Link` components create
accessible anchor tags to route you around the application.

As an example, if the current path is `/user/17`, the following
component will be rendered:

```js
<App activeRoute={
<Users activeRoute={<User params={{userId: 17}} />} />
} />
```

Each component will also receive a `query` prop equal to a dictionary
of the current query params.

Here's the rest of the application:

```js
Expand Down