From 526394bf3a3a0b958c3aa7b24188bcb510be4943 Mon Sep 17 00:00:00 2001 From: Nathaniel Bibler Date: Wed, 26 Aug 2015 11:50:48 -0400 Subject: [PATCH] Fix the link to the Element and Fragment RFC Since the Element and Fragment RFC is contained in a separate branch of this repository - and ideally the link tracks with the latest version of the file - there's no straightforward way to have GitHub auto-link it (that I know of). So, this updates the Markdown link to go to the GitHub blob URL for the current Element and Fragment RFC. --- active/0000-routeable-components.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/active/0000-routeable-components.md b/active/0000-routeable-components.md index 89332196c6..9b4bb014c3 100644 --- a/active/0000-routeable-components.md +++ b/active/0000-routeable-components.md @@ -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 `` and `` (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 `` or `` tag is defining a Component or Fragment. @@ -240,7 +240,7 @@ mean `Component` *or* `Fragment`. To distinguish `Component` templates from `Fragment` templates, we will introduce the `` and `` keywords, which are -described in a [separate RFC document](element-and-fragment). +described in a [separate RFC document][element-and-fragment]. ## Query Parameters @@ -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