Skip to content

Fix the link to the Element and Fragment RFC #3

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
ef4 merged 1 commit into from
Jan 12, 2017
Merged

Fix the link to the Element and Fragment RFC #3

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
6 changes: 4 additions & 2 deletions active/0000-routeable-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ components, the current distinction between the `templates` and
`templates/components` directories becomes unhelpful. We want to put
all of them into just `templates`. Thanks to the introduction of
`<element>` and `<fragment>` (see the
[Element and Fragment RFC](element-and-fragment)), we can make this
[Element and Fragment RFC][element-and-fragment]), we can make this
transition gracefully.

- A template in `templates` with an `<element>` or `<fragment>` tag is defining a Component or Fragment.
Expand Down Expand Up @@ -240,7 +240,7 @@ mean `Component` *or* `Fragment`.

To distinguish `Component` templates from `Fragment` templates, we
will introduce the `<element>` and `<fragment>` keywords, which are
described in a [separate RFC document](element-and-fragment).
described in a [separate RFC document][element-and-fragment].

## Query Parameters

Expand Down Expand Up @@ -486,3 +486,5 @@ renderComponents: function(attributes) {
});
}
````

[element-and-fragment]: https://github.com/ef4/rfcs/blob/element-and-fragment/active/0000-element-and-fragment.md