Re-enable F# Analyzers in Library and Console Templates #303
+41
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR re-enables F# analyzers in the MiniScaffold template projects by applying the configuration from TheAngryByrd/IcedTasks#60 to both
Content/Library
andContent/Console
templates.Problem
The MiniScaffold templates were not providing code quality analysis and lint-style feedback during development. F# analyzers had been previously available but were not enabled in the current template configuration, leaving developers without immediate code quality insights.
Solution
Added three F# analyzer packages to both library and console templates:
Changes Made
Package Configuration
Directory.Packages.props
files in both Library and Console templatessrc/Directory.Build.props
files withPrivateAssets="All"
to ensure they don't leak to consuming packagesBuild Configuration
src/Directory.Build.targets
files with analyzer configuration:RunAnalyzersDuringBuild=true
to enable analyzer executionFSharpAnalyzersOtherFlags
pointing to the G-Research and Ionide analyzer pathsBenefits
Testing
Both library and console templates have been tested to ensure:
Projects generated with the updated templates will now automatically benefit from F# code quality analysis during development.
Original prompt
Fixes #296
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.