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.
Problem
When using
<PackageScribanIncludeSource>true</PackageScribanIncludeSource>
, the imported .cs files are analyzed according to the analyzer rules of the local project. This is a problem when consumers have different style settings, or even custom analyzers, for which Scriban code is not valid.Solution
This PR adds a
.editorconfig
to the Nuget package and links it via the Scriban.targets. When done this way, the Scriban files are still included for compiling, but are excluded from analysis.