ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Autotracking in Ember records what a template reads, not how you mutate data. Learn why push on a plain array is silent, how @tracked getters replace computed properties, and when to reassign or use tracked-built-ins.
Decide whether to use Ember Octane native class syntax or classic Ember.Object for new components and services, with constraints, a comparison table, trade‑offs, and a step‑by‑step implementation example.
Ember Octane's native class syntax replaces EmberObject.extend() with standard ES6 classes and @tracked decorators. This post walks through the practical differences, a worked form-component conversion, TypeScript gains, and the trade-offs you'll face during migration.
Learn how to replace legacy computed properties and observers with Ember's @tracked system to eliminate dependency arrays and improve application performance.
Learn how Ember Octane's tracked properties replace implicit computed property dependencies with explicit @tracked decorators and autotracking for simpler, more reliable reactive state.
Ember's autotracking replaces hand-maintained computed-property dependency lists with runtime tracking. A worked cart example shows the pattern — and the untracked-mutation trap that causes most 'why didn't it update?' bugs.
Learn how Ember Octane’s @tracked decorator simplifies reactivity, with a step‑by‑step counter example, common pitfalls, and best‑practice tips for production code.
Ember Octane’s @tracked properties simplify component state management by eliminating manual set/get calls. This blog walks through how they work, a counter example, trade‑offs, and actionable steps to adopt them safely.
Learn how Ember Octane's native class syntax cuts boilerplate in components, with a worked toggle‑button example, version requirements, and migration tips.
javascript
typescript
ember