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.

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

Fixed typos in RFC 276 #277

Merged
merged 1 commit into from
Dec 11, 2017
Merged

Fixed typos in RFC 276 #277

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
4 changes: 2 additions & 2 deletions text/0276-named-args.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ Since the `{{foo}}` syntax still works on `Ember.Component` (which is the
only kind of components available today) via the auto-reflection mechanism,
we are not really in a rush to migrate the community (and the guides, etc)
to using the new syntax. In the meantime, this could be viewed as a tool to
improve clearity in templates, similar to how the optional "explicit `this`"
improve clarity in templates, similar to how the optional "explicit `this`"
syntax (`{{this.foo}}`).

While we think writing `{{@foo}}` would be a best practice for new code
Expand All @@ -105,7 +105,7 @@ This introduces a new piece of syntax that one would need to learn in order to
understand Ember templates.

This mostly affects "casual" readers (as this should be very easy for an Ember
deverloper to learn, understand and remember after encounting/learning it for
developer to learn, understand and remember after encounting/learning it for
the first time). However, since these casual readers are also among those
who are most acutely affected by the ambiguity, we believe this is still a
net improvement over the status-quo.
Expand Down