"Redundant record update" warning is not useful sometimes

[ffigiel]

When working on a lustre app, I noticed how this warning often comes up in the update function

[1] warning: Redundant record update
[1]    ┌─ /home/filip/code/gleam/yak/yak_ui/src/yak_ui/pages/home.gleam:54:7
[1]    │
[1] 54 │       State(..state, logging_out: False, logout_error: option.Some(err)),
[1]    │       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This record update specifies all fields
[1]
[1] Hint: It is better style to use the record creation syntax.

When building UIs, it's not uncommon to slowly add more features to the app over time. If I was to accept this hint and use the explicit record creation syntax, the app would become painful to manage, as each new field in the State type will require me to update all branches in the update function.
I don't know if this issue is going to be prevalent, but currently it is a bit annoying during development.

I could imagine an emergent (anti-?)pattern of adding a dummy field to the State just to mute this warning.

Let's wait and see how this develops.