Skip to content
This repository was archived by the owner on May 13, 2022. It is now read-only.
This repository was archived by the owner on May 13, 2022. It is now read-only.

RFC #0236 - Tracking for Ember.String deprecation #26

@kategengler

Description

@kategengler

RFC #0236 - Tracking for Ember.String deprecation

Champion: @locks


Expand for Instructions

All teams need to consider a merged RFC to plan any required work. Each team should comment on or edit this with links to issues for the work (or a note to the effect of "No work required").

See the README for more information
See #3 for an example

Under each team, for each repo requiring work for the RFC under that team:
### [repo name](repo url)

- [ ] (issue or pr) description, (issue or pr) link

Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.

Misc

  • investigate if we should build a codemod for moving people off of the Ember.String prototype extension

Ember.js Team

  • ember.js
  • @ember/string
    • extract addon
    • publish to npm
    • deprecate loc
    • Don't include duplicated code (?)
    • publish 2.0 without loc (PR)

Ember CLI Team

Ember Data Team

  • ember-data
    • add @ember/string as a dependency [PR]
    • potentially remove usages of @ember/string?

Learning Team

  • deprecation-app
    • add entry for loc deprecation (PR)
    • add entry for prototype extension deprecation (PR)
    • add entry for Ember.String deprecation (deprecates importing from @ember/string without the addon installed)

Steering Committee

No work required.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions