Update Nested State Without Rebuilding the Whole Object

Flutter screens often render from a state object.

That state gets nested fast. A profile has an address. A cart has shipping details. A form has sections.

Changing one nested field should not make the screen rebuild the whole object by hand.

Dust CopyWith() keeps that small.

When both models derive CopyWith(), Dust can generate a chained helper for the nested field.

You update the field you mean to change. Omitted fields stay as they are.

The model still shows the shape of the state. The repeated update code stays in the generated .g.dart file.

Read the Dust CopyWith behavior guide.

#Dust #DataClass #Flutter #Dart #CodeGeneration