SponsorCheck integration in v33 questions/feedback #1915
martincostello
started this conversation in
General
Replies: 1 comment 1 reply
|
1. Open source exemption. Agreed that $0 is a different thing from "under US$10,000". 33.0.0-beta.8 adds an <PropertyGroup>
<Verify_SponsorshipExemption>OpenSource</Verify_SponsorshipExemption>
<Verify_SponsorshipExemptionUntil>2027-09</Verify_SponsorshipExemptionUntil>
</PropertyGroup>The end month can be at most 12 months out. Docs: https://github.com/VerifyTests/Verify/blob/main/docs/maintenance-fee.md#exempt 2. Suppressing SC031. in your NoWarns are you ensuring each level inherits the parent? eg |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Two pieces of feedback on the SponsorCheck integration in Verify v33:
Is there a missing
SponsorshipExemptiontype for a generic "open source" project? We're using Verify in Swashbuckle.AspNetCore, which I wouldn't really consider to beSmallRevenue- it's MIT-licensed and essentially free and doesn't generate revenue, other than having a GitHub Sponsors link for goodwill donations. We similarly use Verify in the OpenTelemetry .NET SDK, and that doesn't generate revenue and doesn't have GitHub Sponsors. I would consider free/$0 to be distinct from "less than USD 10,000" (even if mathematically 0 < 10000).How do I completely suppress the
SC031warning? I've tried bothNoWarn="SC031"on the CPMPackageVersionitem, thePackageReferenceitems and<NoWarn>$(NoWarn);SC031</NoWarn>inDirectory.Build.props, but in all cases I still get the following warning:I don't want to see any warnings in the build output whatsoever.
All reactions