swe-programming-fsharp

To enforce F# coding standards for AI-generated code, apply mandatory naming conventions like PascalCase for types, require Fantomas formatting, and mandate exhaustive pattern matching. This ensures AI agents write idiomatic F# code aligned with repository-specific quality standards.

Railway-oriented error handling in F# is implemented using discriminated unions and specific domain modeling rules. Following these idiomatic patterns ensures maintainable error handling workflows that comply with established functional programming standards.

Writing F# tests with Expecto and FsCheck involves creating property-based tests for discriminated unions and domain models. This testing approach validates code quality and ensures functional correctness compliant with repository-specific F# testing standards.

Yes, Fantomas formatting is mandatory for F# Giraffe demo applications. It enforces consistent code formatting across the repository, reducing code review overhead and preventing non-compliance with established F# coding standards.

AI agents write inconsistent F# code when lacking enforced coding standards. Without mandatory rules for PascalCase types, Fantomas formatting, and exhaustive pattern matching, generated code fails to meet repository-specific F# quality and formatting requirements.

Yes, async workflows can be used with discriminated unions in F# domain modeling. This combination is part of idiomatic F# development, enabling robust asynchronous operations while maintaining type safety and exhaustive pattern matching compliance.