Add XML doc standards; enable compiler-generated files

Added "XML Documentation" section to CONVENTIONS.md, specifying usage of <summary> tags for developer-facing comments and restricting implementation details to external docs. Enabled EmitCompilerGeneratedFiles in FruitBank.Common.csproj for improved debugging and analysis.
This commit is contained in:
Loretta 2026-05-23 09:27:29 +02:00
parent b61b8085df
commit 92296c479b
1 changed files with 4 additions and 0 deletions

View File

@ -18,6 +18,10 @@ Follow the doctrine in `../AyCode.Core/docs/CONVENTIONS.md#framework-first-place
- **Services:** `Ac{Domain}ServiceBase` for abstract bases. Platform-specific implementations in consuming projects. - **Services:** `Ac{Domain}ServiceBase` for abstract bases. Platform-specific implementations in consuming projects.
- **ViewModels:** In `AyCode.Blazor.Models/ViewModels/` — suffixed with `ViewModel` or kept as plain model classes. - **ViewModels:** In `AyCode.Blazor.Models/ViewModels/` — suffixed with `ViewModel` or kept as plain model classes.
## XML Documentation
`<summary>` — brief, developer-facing, readable in VS IntelliSense tooltip. NO implementation details, NO wire-format / byte-level / perf specifics — those live in `docs/TOPIC/*.md`. Add `<example>` only when usage is non-obvious; otherwise omit.
## Component Patterns ## Component Patterns
- **DevExpress 25.1.3 exclusively** — never mix with other Blazor component libraries. - **DevExpress 25.1.3 exclusively** — never mix with other Blazor component libraries.