RFC #0324 - Tracking for Deprecate Component#isVisible

[kategengler]

RFC #0324 - Tracking for Component#isVisible

Champion: @rwjblue

---

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.

Ember.js Team:

ember.js

• introduce deprecation (Deprecate Component#isVisible ember.js#17918)
• remove deprecation in until release

Ember CLI Team:

N/A

Ember Data Team:

N/A

Learning Team:

ember.js

• check deprecated flag is displayed correctly in API Docs once deprecation is introduced
• check that isVisible API description from the API Docs is removed successfully once deprecation is outlived

deprecation-app

• add a deprecation to the deprecations app

guides-source

• check guides-source for instances of isVisible and if applicable remove / replace the mentions in code examples with the alternative mentioned in the RFC

Steering Committee:

N/A

[jayjayjpg]

Just had a quick look at the Guides and saw that there's no mention of Component#isVisible - we should be able to check this one off the list of learning items

[rwjblue]

@GavinJoyce has a PR up over in emberjs/ember.js#17948

[sandstrom]

@kategengler I think we can close this issue, or at least mark some subpoints as completed:

• introduce deprecation
• add a deprecation to the deprecations app

This was worked on in: emberjs/ember.js#17948