Pass dump-symbol-graph flags to symbolgraph-extract

[Dev1an]

Passes flags from swift package dump-symbol-graph to swift-symbolgraph-extract

Motivation:

The package manager allows us to extract a symbol graph from a Swift Package without the need to manually specify the module-name, target, sdk and other compiler flags. But it is limited to extract public symbols only, because it takes away the ability to specify any of the swift-symbolgraph-extract configuration options (like access control etc.).
This pull request adds some of the most useful configuration options of swift-symbolgraph-extract to the SPM tool and passes them through.

Modifications:

The following flags are added to the DumpSymbolGraph: SwiftCommand:

• prettyPrint: Bool
• skipSynthesisedMembers: Bool
• minimumAccessLevel: AccessLevel
• skipInheritedDocs: Bool
• includeSpiSymbols: Bool

AccessLevel is a new struct that I declared in the SymbolGraphExtract.swift file.

Result:

You can now dump symbol graphs with SPM

• using pretty-printed formatting
• skipping synthesised members
• using user-defined minimum access levels: private, fileprivate, internal, open
• skipping inherited docs
• including SPI symbols

Usage instructions can be shown by executing swift package dump-symbol-graph --help

OVERVIEW: Dump Symbol Graph

USAGE: swift package dump-symbol-graph <options>

OPTIONS:
  --pretty-print          Pretty-print the output JSON. 
  --skip-synthesized-members
                          Skip members inherited through classes or default implementations. 
  --minimum-access-level <minimum-access-level>
                          Include symbols with this access level or more. Possible values: private | fileprivate | internal | public | open (default:
                          public)
  --skip-inherited-docs   Skip emitting doc comments for members inherited through classes or default implementations. 
  --include-spi-symbols   Add symbols with SPI information to the symbol graph. 
  --version               Show the version.
  -help, -h, --help       Show help information.

[tomerd]

@abertelrud this is something that we should refactor out to a plugin when the underlying framework is in place. could you please review in that light.

[tomerd]

@swift-ci please smoke test

[abertelrud]

I believe that the unit test failure is unrelated. I think I saw a different PR that resolves it, so probably just running the tests again after your amended fix will result in green builds.

[Dev1an]

OK I amended a formatting change. I now

• used SPI instead of Spi
• switched my indentation style from tabs to spaces to match the rest of the code.

Can someone retrigger the smoke test @tomerd @abertelrud?

[neonichu]

@swift-ci please smoke test

[abertelrud]

Looks good to me. Thanks!

[abertelrud]

@neonichu @tomerd Ok to merge?