|
| 1 | +# Console Report Format Example Scripts |
| 2 | + |
| 3 | +This directory contains scripts used to generate the console output screenshots shown in the Console report format documentation. |
| 4 | + |
| 5 | +## Purpose |
| 6 | + |
| 7 | +These scripts allow reproducing the console output examples to: |
| 8 | +- Regenerate screenshots when the addin is updated |
| 9 | +- Test different console formatting options |
| 10 | +- Validate console output behavior |
| 11 | + |
| 12 | +## Scripts |
| 13 | + |
| 14 | +- `generate-default.cake` - Default console output settings |
| 15 | +- `generate-grouped.cake` - Console output grouped by rule |
| 16 | +- `generate-summaries.cake` - Console output with provider and priority summaries |
| 17 | +- `generate-combined.cake` - Console output with all features enabled |
| 18 | +- `sample-issues.json` - Sample issues data used by all scripts |
| 19 | + |
| 20 | +## Usage |
| 21 | + |
| 22 | +To regenerate the console output for screenshots: |
| 23 | + |
| 24 | +1. Ensure the latest Cake.Issues packages are built: |
| 25 | + ```bash |
| 26 | + cd /path/to/Cake.Issues |
| 27 | + ./build.sh --target=Create-NuGet-Packages |
| 28 | + ``` |
| 29 | + |
| 30 | +2. Run any of the example scripts: |
| 31 | + ```bash |
| 32 | + cd docs/input/assets/scripts/console-examples |
| 33 | + dotnet tool restore |
| 34 | + dotnet tool run dotnet-cake generate-default.cake --verbosity=minimal |
| 35 | + ``` |
| 36 | + |
| 37 | + Or run all examples at once: |
| 38 | + ```bash |
| 39 | + ./run-examples.sh |
| 40 | + ``` |
| 41 | + |
| 42 | +3. Capture the console output for documentation screenshots |
| 43 | + |
| 44 | +## Example Output |
| 45 | + |
| 46 | +To see the individual issue details, run with normal verbosity. To see just the summaries (as shown in the screenshots), use `--verbosity=minimal`. |
| 47 | + |
| 48 | +## Sample Data |
| 49 | + |
| 50 | +The `sample-issues.json` file contains realistic issue data representing: |
| 51 | +- MSBuild compiler warnings and suggestions |
| 52 | +- DupFinder duplicate code detection issues |
| 53 | +- InspectCode style and best practice violations |
| 54 | +- markdownlint documentation issues |
| 55 | +- Custom script issues |
| 56 | + |
| 57 | +This data produces output similar to what users would see in real projects. |
0 commit comments