Odoo computes beat onchanges on determinism/data validation. But in complex cases (_inherits sync dynamic aml in BR localization) you will end up fighting the ORM introducing context flags to skip them. In the end the benefit is here but smaller than you initially thought...

So after I replaced 80% of legacy onchanges by precompute, I just migrated a dozen of most important OCA Brazilian localisation modules to version 17.0. It was really straightforward; v18 coming... cc @OdooCommunity

FYI, soon we will have replaced 75% of the dozens of onchanges by compute/precompute in the OCA Brazilian fiscal module of Odoo. But we cannot do it for the ~200 tax fields (Brazil tax are crazy...) because it woukd become 50% slower than with today's onchange. cc @OdooCommunity

Zonelessにして驚くほどLighthouseでのパフォーマンスが改善してるんだけど（実測値）、こんなに変わる？！ってなってる。Zone-basedの方も、app.component.ts以外は全部OnPush戦略になってるんだけど。 とりあえず表示完了までのOnChangesの実行回数でも数えるかな・・・。

🚀 Angular Signal Inputs vs @Input: The future of reactivity in Angular! 🌐 Signal inputs, introduced in Angular 17.1, are a game-changer! They simplify reactivity and replace the need for OnChanges. No more manual updates when your input changes. Here’s how to refactor @Input to signal input: @Component({ selector: "counter", standalone: true, template: ` <h1>Counter value: {{ value() }}</h1>`, }) export class CounterComponent { value = input(0); } ✅ Less boilerplate ✅ Simpler code ✅ No more OnChanges lifecycle! Want to dive deeper? Check out the full guide! 🔗blog.angular-university.io/a… #Angular #WebDev #Frontend

🚀 Angular's Signal Components API – A Game-Changer! Angular 17.3 introduces a cleaner, more reactive way to define components: ✅ input() → Replaces @Input() ✅ output() → Type-safe alternative to @Output() ✅ model() → Simplifies two-way binding No more OnChanges, better RxJS integration & type safety! Example: class BookComponent { book = input.required<Book>(); deleteBook = output<Book>(); onDelete() { this.deleteBook.emit(this.book()); } } Full guide 👇 🔗 blog.angular-university.io/a… #Angular #WebDev #Frontend

She couldn’t even spell misspelling correctly. I’m sure she will say it was on purpose just like her spelling of Tesla.

I hope you guys on the left/liberal side keep acting like this. It’s great! You guys will not be in power again every day Americans see how mentally retarded you are

They know that it’s because Trump keeps miss spelling it !

Stfu and join the army and make Zelenskyy your new president.

Forgot to remove "implements OnChanges" 😇

@DevVersion @marktechson thank you for the new blog post about the signal input migration. By the way, someone pointed out that the `implements OnChanges` was left in the post-refactor reddit.com/r/Angular2/commen…

Dive into Angular component lifecycle! Explore how OnInit, OnChanges, and OnDestroy hooks enhance flexibility in your Angular apps. #DEVCommunity #Angular dev.to/moh_moh701/angular-fu…

Not sure if thing has changed, but this is a nice way to improve type when using OnChanges in Angular! Since `changes[key].currentValue` will return type as any without this! Thanks, @NetanelBasal

What do you call it when you click a button and nothing reacts? A broken app. Reactive programming does not describe a mechanism or behavior. It's a way to organize code. Any pattern involving a function with no return is not reactive. Event handlers are not reactive. Callback functions are not reactive. createEffect, useEffect, effect, $scope.$watch - none of these are reactive. OnInit, OnChanges, OnDestroy - not reactive. onClick, onChange, onSubmit - not reactive. createSignal, useState, signal - not reactive. let, var - not reactive. BehaviorSubject, ReplaySubject, Subject - not reactive. subscribe, then - not reactive. createMemo, computed, pipe, [attr]="value", {{ value }} - reactive!

Yup, I hope (also in the other thread), that we corrected/clarified that. Thanks. What's still missing is to sell Sergey on the new API: I've come up with the following arguments. Maybe you can extend the list: ✅ (Finally) a required for inputs which remove the union type with ‘undefined’ ✅ No hooks like AfterViewInit, OnInit, OnChanges - just computed and effect ✅ Reduction of ExpressionChangedError (see @Jean__Meche posting) ✅ Reactive Inputs ✅ "Banana Box" Syntax support writable Signals ✅ Simpler two-way binding via model (no need to remember the naming convention [propertyName]Change) ✅ Signals enforce immutable changes (common bug with OnPush and property binding) ✅ automatic markForCheck via Signal changes (will already work for zoneless apps with the upcoming async scheduler) ✅ Local change detection

100% agree. I don’t like the idea of using an effect for this reason. Let’s say I need to fetch data based on id passed in via input. For state I’m using NgRx SignalStore. As far as native solutions go, I can: 1. Use signal inputs effect to invoke the SignalStore method that fetches data. I have to use allowSignalWrites to do this. 2. Use the Input directive setter to invoke the SignalStore method that fetches data 3. Use the OnChanges life cycle hook to invoke the SignalStore method Personally, I went with the first option because based on the RFC that seems more aligned with the Angular team’s vision for signal components. Which would you choose? Do you see another option I haven’t considered. Thanks for the food for thought!

If you i.e. rely on OnInit for processing input data then you will miss data updates with trackBy. That said rather use OnChanges and trackBy if you can

Hello @angular. Did you noticed that OnChanges lifecycle hook is the only one which can be called multiple times? Probably that's why it has hidden complexity 😉 Do you prefer setters for inputs instead? Or you still love OnChanges ? :)