Skip to content
Merged
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions text/0558-edition-detection.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,20 +8,20 @@
## Summary

Introduces a mechanism that an application can use to specify which Edition of
Ember it is intending to target. This RFC will define:
Ember it intends to target. This RFC will define:

* How to specify the edition that the application is using
* How other packages (addons, codemods, etc) can detect the applications intended edition
* What the edition should be used for

## Motivation

As Ember approaches it's first edition (see
As Ember approaches its first edition (see
[emberjs/rfcs#364](https://github.com/emberjs/rfcs/pull/364)) various addons
need to modify their behavior based on the edition that is being used. An
initial implementation (done without RFC) used the `setEdition` method from
`@ember/edition-utils` inside the application's (or addon's) `.ember-cli.js`
file to specify which edition was to be used. That implementation worked well
`@ember/edition-utils` inside the application or addon's `.ember-cli.js`
file to specify which edition to use. That implementation worked well
enough throughout the intial preview period, but a number of major issues were
(rightfully!) surfaced by the community:

Expand Down