chore: add ability to skip-validation + simplify unicode logging

[david-pw]

Description

When attempting to use Refitter.MSBuild I ran into an issue where the generated file wasn't being produced. Upon further investigation using dotnet build -verbosity:Detailed it was found that I was running into a validation issue that prevented the files from being generated.

This PR gives the consumer that ability to optionally SkipValidation as needed.

As an aside, MSBuild logging has been forcefully set to simple-output to ensure readable logging.

Additional Info

#762
#763

Summary by CodeRabbit

• New Features

  • Added an option to skip validation during generation, letting configured builds bypass validation.
  • Build output is now simplified for clearer, more readable logs.

• Documentation

  • MSBuild usage examples updated to show the new skip-validation parameter.

[coderabbitai]

Walkthrough

Adds a SkipValidation flag to the MSBuild task and wiring, updates README usage, and modifies the task to always pass --simple-output and optionally --skip-validation to the dotnet process. No other control flow or exported API changes.

Changes

Cohort / File(s)	Summary of changes
MSBuild task implementation src/Refitter.MSBuild/RefitterGenerateTask.cs	Adds public bool SkipValidation { get; set; }; StartProcess now quotes DLL and settings paths, always includes --simple-output, and appends --skip-validation when SkipValidation is true.
MSBuild wiring & docs src/Refitter.MSBuild/Refitter.MSBuild.targets, src/Refitter.MSBuild/README.md	Task invocation and README updated to pass SkipValidation="$(RefitterSkipValidation)"; UsingTask formatting adjusted with no behavioral changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant MSBuild
  participant Task as RefitterGenerateTask
  participant DotNet as dotnet (Refitter CLI)

  MSBuild->>Task: Invoke with DisableLogging, SkipValidation
  activate Task
  Note right of Task #e8f6ff: Build args include --simple-output\nAdd --skip-validation if true
  Task->>DotNet: dotnet exec "refitter.dll" "settings.json" --simple-output [--skip-validation]
  activate DotNet
  DotNet-->>Task: stdout/stderr, exit code
  deactivate DotNet
  Task-->>MSBuild: Task result
  deactivate Task

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

.NET

Poem

I hop through targets, quick and small,
A little flag to skip the call.
Simple output lights the way,
Validation naps for just today.
Builds hop onward — carrot, hooray! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly captures the two main changes in this PR—the introduction of a skip-validation option and a simplification of logging output—aligning with the added SkipValidation parameter and the new --simple-output flag in the task invocation. It is concise, clear, and directly reflects the core enhancements without extraneous detail.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between df07553 and 249d2bf.

📒 Files selected for processing (1)

• src/Refitter.MSBuild/RefitterGenerateTask.cs (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/Refitter.MSBuild/RefitterGenerateTask.cs

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/Refitter.MSBuild/README.md (1)

12-15: Clarify how to set RefitterSkipValidation.

Nice to see the new switch exposed here. Could we add a short note right below this snippet explaining how to set <RefitterSkipValidation>true</RefitterSkipValidation> in a project file and what behaviour to expect? That will keep the docs self-contained for folks scanning this page.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 770444f and df07553.

📒 Files selected for processing (3)

• src/Refitter.MSBuild/README.md (1 hunks)
• src/Refitter.MSBuild/Refitter.MSBuild.targets (1 hunks)
• src/Refitter.MSBuild/RefitterGenerateTask.cs (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/**/*.cs

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

src/**/*.cs: Follow existing C# coding conventions defined in .editorconfig
Use PascalCase for public members
Use camelCase for parameters and local variables
Include XML documentation for public APIs
Use meaningful variable and method names

Files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs

🧠 Learnings (3)

📚 Learning: 2025-09-17T20:15:55.708Z

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-09-17T20:15:55.708Z
Learning: Applies to src/Refitter.Core/Settings/RefitGeneratorSettings.cs : Add corresponding property to src/Refitter.Core/Settings/RefitGeneratorSettings.cs for new CLI options

Applied to files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs
• src/Refitter.MSBuild/README.md
• src/Refitter.MSBuild/Refitter.MSBuild.targets

📚 Learning: 2025-09-17T20:15:55.708Z

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-09-17T20:15:55.708Z
Learning: Applies to src/Refitter/Program.cs : CLI entry point resides at src/Refitter/Program.cs; ensure changes affecting CLI startup are made here

Applied to files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs

📚 Learning: 2025-09-17T20:15:55.708Z

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-09-17T20:15:55.708Z
Learning: Applies to src/Refitter/GenerateCommand.cs : Map new CLI option in CreateRefitGeneratorSettings() within src/Refitter/GenerateCommand.cs

Applied to files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs

🔇 Additional comments (1)

src/Refitter.MSBuild/Refitter.MSBuild.targets (1)

8-10: Forwarding the SkipValidation flag looks good.

Thank you for wiring the MSBuild property straight through to the task—this keeps the new CLI flag accessible to build consumers without changing the rest of the target flow.

[christianhelle]

@all-contributors please add @david-pw for code

[allcontributors]

@christianhelle

I've put up a pull request to add @david-pw! 🎉

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[christianhelle]

@david-pw Thanks for the contribution