File: DocumentationCoverageOptionsArgument.swift

package info (click to toggle)
swiftlang 6.1.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,532 kB
  • sloc: cpp: 9,901,743; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (96 lines) | stat: -rw-r--r-- 4,502 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
/*
 This source file is part of the Swift.org open source project

 Copyright (c) 2021-2024 Apple Inc. and the Swift project authors
 Licensed under Apache License v2.0 with Runtime Library Exception

 See https://swift.org/LICENSE.txt for license information
 See https://swift.org/CONTRIBUTORS.txt for Swift project authors
*/

import ArgumentParser
import Foundation
import SwiftDocC

/// Resolves and validates the arguments needed to enable the documentation coverage feature.
///
/// These options are used by the ``Docc/Convert`` subcommand.
public struct DocumentationCoverageOptionsArgument: ParsableArguments {
    public init() {}

    fileprivate static let noCoverage = DocumentationCoverageOptionsArgument()

    // The way the '--experimental-documentation-coverage' flag and the '--coverage-summary-level' option work together
    // doesn't match the possible values for `DocumentationCoverageLevel`.
    
    @Flag(
        help: ArgumentHelp("Generate documentation coverage output.", discussion: """
        Detailed documentation coverage information will be written to 'documentation-coverage.json' in the output directory.
        """)
    )
    var experimentalDocumentationCoverage: Bool = false

    /// The desired level of documentation coverage. Options are `none`, `brief`, and `detailed`. The default is `.brief`
    @Option(
        name: .customLong("coverage-summary-level"),
        help: ArgumentHelp("The level of documentation coverage information to write on standard out.", discussion: """
        The '--coverage-summary-level' level has no impact on the information in the 'documentation-coverage.json' file.
        The supported coverage summary levels are 'brief' and 'detailed'.
        """,
        valueName: "symbol-kind")
    )
    var summaryLevel: DocumentationCoverageLevel = .brief

    var effectiveSummaryLevel: DocumentationCoverageLevel {
        guard experimentalDocumentationCoverage else {
            return .none
        }
        switch summaryLevel {
        case .detailed:
            return .detailed
        case .none, .brief:
            return .brief
        }
    }
    
    @Option(
        name: .customLong("coverage-symbol-kind-filter"),
        parsing: ArrayParsingStrategy.upToNextOption,
        help: ArgumentHelp("Filter documentation coverage to only analyze symbols of the specified symbol kinds.", discussion: """
        Specify a list of symbol kind values to filter the documentation coverage to only those types symbols.
        The supported symbol kind values are: \ 
        \(DocumentationCoverageOptions.KindFilterOptions.BitFlagRepresentation.allValueStrings.sorted().joined(separator: ", "))
        """,
        valueName: "symbol-kind")
    )
    public var symbolKindFilter: [DocumentationCoverageOptions.KindFilterOptions.BitFlagRepresentation] = []
    
    public mutating func validate() throws {
        Docc.Convert.warnAboutDeprecatedOptionIfNeeded("level", message: "Use '--coverage-summary-level' instead.")
        Docc.Convert.warnAboutDeprecatedOptionIfNeeded("kinds", message: "Use '--coverage-symbol-kind-filter' instead.")
    }
}

// Use fully-qualified types to silence a warning about retroactively conforming a type from another module to a new protocol (SE-0364).
// The `@retroactive` attribute is new in the Swift 6 compiler. The backwards compatible syntax for a retroactive conformance is fully-qualified types.
//
// It is safe to add a retroactively conformance here because the other module (SwiftDocC) is in the same package.
//
// These conforming types are defined in SwiftDocC and extended in SwiftDocCUtilities, because SwiftDocC doesn't link against ArgumentParse (since it isn't about CLI).
// We conform here because this is the first place that we can add the conformance. The implementation is in SwiftDocC.
extension SwiftDocC.DocumentationCoverageLevel: ArgumentParser.ExpressibleByArgument {}
extension SwiftDocC.DocumentationCoverageOptions.KindFilterOptions.BitFlagRepresentation: ArgumentParser.ExpressibleByArgument {}

extension DocumentationCoverageOptions {
    public init(from arguments: DocumentationCoverageOptionsArgument) {
        guard arguments.experimentalDocumentationCoverage else {
            self = .noCoverage
            return
        }
        
        self = DocumentationCoverageOptions(
            level: arguments.effectiveSummaryLevel,
            kindFilterOptions: .init(bitFlags: arguments.symbolKindFilter)
        )
    }
}