Skip to content
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.

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

#588 components/contextual-components #614

Merged

Conversation

betocantu93
Copy link
Contributor

@@ -1,32 +1,32 @@
The
[`{{component}}`](https://www.emberjs.com/api/ember/release/classes/Ember.Templates.helpers/methods/component?anchor=component)
helper can be used to defer the selection of a component to run time. The
`<MyComponent />` syntax always renders the same component, while using the
`<MyComponent/>` syntax always renders the same component, while using the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jenweber @pzuraq is this the style we should use throughout the guides? No space?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya, we should have a space here.

Suggested change
`<MyComponent/>` syntax always renders the same component, while using the
`<MyComponent />` syntax always renders the same component, while using the

@@ -1,32 +1,32 @@
The
[`{{component}}`](https://www.emberjs.com/api/ember/release/classes/Ember.Templates.helpers/methods/component?anchor=component)
helper can be used to defer the selection of a component to run time. The
`<MyComponent />` syntax always renders the same component, while using the
`<MyComponent/>` syntax always renders the same component, while using the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya, we should have a space here.

Suggested change
`<MyComponent/>` syntax always renders the same component, while using the
`<MyComponent />` syntax always renders the same component, while using the

`{{component}}` helper allows choosing a component to render on the fly. This is
useful in cases where you want to interact with different external libraries
depending on the data. Using the `{{component}}` helper would allow you to keep
different logic well separated.

The first parameter of the helper is the name of a component to render, as a
string. So `{{component 'blog-post'}}` is the same as using `<BlogPost />`.
string. So `{{component 'blog-post'}}` is the same as using `<BlogPost/>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
string. So `{{component 'blog-post'}}` is the same as using `<BlogPost/>`.
string. So `{{component 'blog-post'}}` is the same as using `<BlogPost />`.

Copy link
Contributor

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for working on this! Just two small tweaks / suggestions then this is good to go...

Copy link
Contributor

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@rwjblue rwjblue merged commit fe729b6 into ember-learn:octane Mar 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants