mds-bon-patterns

Standardize bon builder usage by using direct setters like `.request_id(...)` instead of `.maybe_request_id(Some(...))` for known values, ensuring clarity and adherence to Bon guide conventions.

The best way to handle optional members in a bon builder is to use direct setters like `.request_id(...)` instead of `.maybe_request_id(Some(...))` for known values, ensuring clarity and adherence to Bon guide conventions.

Bon builder pattern usage focuses on constructing complex configuration objects with standardized setters, whereas Statum-based workflows follow a different state management approach that this standardization explicitly distinguishes from.

Yes, you can use bon builders for conditional object construction in Rust by following repository-standard API selection rules that guide readability and consistency when building complex objects conditionally.

Your bon builder code lacks consistency because it does not enforce repository-standard conventions for optional members, conditional building, and API selection, leading to varied setter usage and reduced maintainability.