DEV Community: dust

Keep Form Validation Rules Close to the Model

YeLinAung — Fri, 21 Aug 2026 03:12:24 +0000

Flutter forms usually start with TextFormField.validator. That works well for one field on one screen.

The problem starts when the same rule appears in more than one place. Signup. Profile edit. Checkout. Tests.

Dust lets the model own the rule. Add Validate() to the model, put the field rule beside the field, and run dust build.

Then the form can call the generated validator helper. The model can still validate itself before submit.

Read the Dust validation guide.

Dust #Validation #Flutter #Dart

Decode Tagged JSON into a Sealed Model

YeLinAung — Sun, 16 Aug 2026 13:15:38 +0000

How do you decode tagged JSON into a sealed model?

Without code generation, you usually read the discriminator and map each value yourself. With Dust, define the tag and variants on the sealed class. Dust generates the JSON helpers, while your app can keep using a normal exhaustive switch.

See the Dust sealed-class guide.

Dust #Serde #Dart #CodeGeneration

Reject JSON Keys You Did Not Ask For

YeLinAung — Sun, 16 Aug 2026 13:15:36 +0000

Extra JSON keys can hide a server and client mismatch. Add disallowUnrecognizedKeys: true to a Dust Serde model. Decoding then rejects any key that is not a field or alias instead of silently accepting it.

Read the Dust Serde configuration guide.

Dust #Serde #JSON #CodeGeneration

Switch API Environments Without a Second Client

YeLinAung — Sun, 16 Aug 2026 13:15:03 +0000

Dust HTTP clients can keep one default API URL and accept a factory override for staging, tests, or local development. The endpoint declarations stay in one interface. Only the URL changes when the client is created.

Read the Dust HTTP client configuration guide.

Dust #HTTPClient #CodeGeneration

Keep Nested Validation on the Full Path

YeLinAung — Sun, 16 Aug 2026 13:15:00 +0000

Dust can validate one model inside another. Add @Validate(nested: true) to the parent field. If Address.zipCode fails, the parent returns address.zipCode, so the error still points to the exact field.

Read the Dust nested validation guide.

Dust #Validation #CodeGeneration

Keep Unix Timestamps at the API Boundary

YeLinAung — Sun, 16 Aug 2026 13:14:26 +0000

When an API sends integer milliseconds, one SerDeCodec<DateTime, int> keeps the JSON unchanged while the model works with DateTime. Apply it to required or nullable fields; Dust handles null outside the codec.

Read the Dust custom codec guide.

Dust #Serde #SerDeCodec #CodeGeneration

Keep Code Generation Running While You Work

YeLinAung — Sun, 16 Aug 2026 13:14:24 +0000

Use Dust watch mode while editing models and APIs. It runs generation after source changes, so generated files stay current without another manual command after every save.

Read the Dust usage guide.

Dust #DustWatch #CodeGeneration

Move One Data Model to Dust

YeLinAung — Sun, 16 Aug 2026 13:13:51 +0000

Move one plain data model to Dust and generate only what it needs, such as equality, copyWith, or toString. Keep the model tests and remove old dependencies only after the migration is complete.

Read the Dust data-class guide.

Dust #DataClass #CodeGeneration

JSON Field Aliases

YeLinAung — Sun, 16 Aug 2026 13:13:47 +0000

Dust can read an old JSON field name while writing the new one. Add an alias for the old key and keep one canonical key for new payloads.

Read the Dust JSON guide.

Dust #Serde #JSON #CodeGeneration

Cross-Field Model Validation

YeLinAung — Sun, 16 Aug 2026 13:11:52 +0000

Dust can keep cross-field rules beside the model. A password confirmation field can point to the password field, so the relationship stays clear and generated validation reports the field error.

Read the Dust validation guide.

Dust #Validation #CodeGeneration

Generate HTTP Request Tests

YeLinAung — Sun, 16 Aug 2026 13:11:49 +0000

Dust can generate request tests with an HTTP client. The tests check the method, path, headers, query values, and request body without calling a live server.

Read the Dust HTTP client guide.

Dust #HTTPClient #CodeGeneration

One Workflow for Dust Features

YeLinAung — Sun, 16 Aug 2026 13:08:48 +0000

Dust gives one generation workflow for data classes, JSON, validation, HTTP clients, routing, state, localization, and database work. The image shows a representative dependency comparison, not a feature-parity claim.

Explore the Dust feature guides.

Dust #CodeGeneration #DeveloperTools