Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce Polly.Core #1053

Merged
merged 7 commits into from
Mar 14, 2023
Merged

Introduce Polly.Core #1053

merged 7 commits into from
Mar 14, 2023

Conversation

martintmk
Copy link
Contributor

@martintmk martintmk commented Mar 13, 2023

The issue or feature being addressed

This PR adds a new Polly.Core project where the V8 API will be implemented.

Right from the start we want to enforce high code quality by:

  • Using the extended set of rules for StyleCop and .NET Analyzers. Enabling this for existing project would cause a lot of pain, however, here it's easy to follow.
  • Enforcing 100% code coverage

Details on the issue fix or feature implementation

This PR prepares the Polly builds for the new project and does some cleanup around the build infrastructure. Mostly just moving some MSBuild properties to a props/targets to promote the reusability.

The size of this PR is somehow inflated because of the analyzer rules in eng/analyzers, these are just recommended rules I copied from our code base and that we are using in production libraries.

Confirm the following

  • I started this PR by branching from the head of the default branch
  • I have targeted the PR to merge into the default branch
  • I have included unit tests for the issue/feature
  • I have successfully run a local build

@martintmk martintmk changed the title Mtomka/introduce polly.core Introduce Polly.Core Mar 13, 2023
.editorconfig Outdated Show resolved Hide resolved
src/Polly.Core.Specs/Polly.Core.Specs.csproj Outdated Show resolved Hide resolved
src/Polly.Core.Specs/Polly.Core.Specs.csproj Outdated Show resolved Hide resolved
<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFrameworks>netstandard2.0;net461;net472;net6.0;net7.0</TargetFrameworks>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you need net472 here.

And in general, I recommend listing the TFMs from most recent to oldest. That way, when VS opens up, it will default to showing you the latest TFM.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, adjusted these.

@martintmk martintmk merged commit 32cf92f into main Mar 14, 2023
@martincostello martincostello deleted the mtomka/introduce-polly.core branch March 14, 2023 17:29
@martincostello martincostello added this to the v8.0.0 milestone Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants