Package Cratis.Architecture.CodeAnalysis as a Roslyn analyzer#11
Open
woksin wants to merge 1 commit into
Open
Conversation
Configure the project to pack as a proper analyzer so the publish workflow produces a usable NuGet package: target netstandard2.0, set IncludeBuildOutput=false and DevelopmentDependency, and pack the assembly into analyzers/dotnet/cs instead of lib/. Targeting netstandard2.0 requires a few compatibility fixes: add minimal System.Index/System.Range polyfills for the range operators and replace char overloads of string.Split/Join/Replace/StartsWith not available on netstandard2.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Makes the
Cratis.Architecture.CodeAnalysispackage install correctly as a Roslyn analyzer so the publish workflow produces a usable package.Fixed
Cratis.Architecture.CodeAnalysispackage now ships the analyzer inanalyzers/dotnet/cs(targeting netstandard2.0) instead oflib/, so the analyzers actually load and run in consuming projects and IDEs.