auto-silent-defaults

Substituting default values masks missing data, causing silent failures and hard-to-trace bugs. Enforcing strict validation surfaces missing required fields as errors and returns null for optional fields, ensuring deterministic behavior in production.

Fail immediately on missing required data to expose errors early, return null for optional fields, and apply safe defaults only when guaranteed appropriate. This ensures deterministic behavior across config loading, data parsing, and function results.

Refactor code to eliminate unwrap_or_default patterns by enforcing strict validation rules. Surface missing required data as errors, propagate null for optional fields, and apply conservative defaults only when explicitly appropriate.

Yes, this validation discipline applies across config loading, data parsing, and function results. It enforces failing on missing required data and returning null for optional data to ensure deterministic behavior throughout your application.

Avoid using defaults when data is required for startup or critical operations. Defaulting should only occur when guaranteed appropriate; required fields must surface as errors to prevent silent failures and maintain conservative defaulting rules.