jstedfast / MimeKit
94%
master: 94%

LAST BUILD BRANCH: mime-compliance-violations
DEFAULT BRANCH: master
Repo Added
Files 197
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH mime-compliance-violations
branch: SELECT
CHANGE BRANCH
x

coverage: 94.171% (+94.2%) from 0.0%
4.14.0.1882

push

coveralls.net

jstedfast 
Changed validator API to use Write() and Validate()

33343 of 35407 relevant lines covered (94.17%)

0.94 hits per line

Relevant lines Covered
35407 RELEVANT LINES 33343 COVERED LINES
0.94 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
4.14.0.1882 mime-compliance-violations Changed validator API to use Write() and Validate() push jstedfast coveralls.net
94.17
4.14.0.1875 master Upgrade .NET SDK setup actions to version 5 push web-flow coveralls.net
94.08
4.14.0.1874 mime-compliance-violations Changed validator API to use Write() and Validate() push jstedfast coveralls.net
0.0
4.14.0.1873 master Add .NET 10 SDK installation to workflow Added installation step for .NET 10 SDK alongside .NET 8 SDK. push web-flow coveralls.net
94.17
4.14.0.1872 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.08
4.14.0.1871 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.08
4.14.0.1870 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.08
4.14.0.1869 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.08
4.14.0.1868 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.08
4.14.0.1867 mime-compliance-violations Started adding encoding validation logic TODO: Should we have a different MimeComplianceViolation for each encoding? Or should we just have InvalidEncodedContent? What about a different enum value for each kind of invalid encoding state? push jstedfast coveralls.net
94.07
See All Builds (2654)