Skip to content

Conversation

wagenet
Copy link
Contributor

@wagenet wagenet commented Aug 12, 2025

No description provided.

Copy link

netlify bot commented Aug 12, 2025

Deploy Preview for ember-deprecations ready!

Name Link
🔨 Latest commit 873ba72
🔍 Latest deploy log https://app.netlify.com/projects/ember-deprecations/deploys/689b80ff20c67f0008932c81
😎 Deploy Preview https://deploy-preview-1412--ember-deprecations.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@wagenet wagenet mentioned this pull request Aug 12, 2025
11 tasks
It created a second property that reflected another property's value.

## Migration
Prefer direct access to the original tracked state, or use a simple getter and setter.
Copy link
Contributor

Choose a reason for hiding this comment

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

alias could point to a computed property, a getter, or really anything so this may need to describe how make sure they work going forward.

```
After:
```js
class Cart {
Copy link
Contributor

Choose a reason for hiding this comment

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

This needs reactivity

import ComputedProperty from '@ember/object/computed';
// rarely used directly
```
After: Remove the import; refactor any custom meta-programming to simple getters.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think custom ComputedProperties weren't rare.

```
After:
```js
import { isEmpty } from '@ember/utils';
Copy link
Contributor

Choose a reason for hiding this comment

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

@ef4
Copy link
Contributor

ef4 commented Aug 29, 2025

RFC review notes:

  • landing this deprecation is valuable because it teaches people to stop making new ones
  • this one might be hard to clear, so we would consider giving it a longer time before removal
  • before removal, we should strongly consider shipping some tools to help automate the migration
  • we probably need to document what addons to upgrade before you attempt this (since dependency chains might bottom out down in addons)

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