You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Deprecate `DocumentationConverter`
* Update DataProvider protocol to a be general purpose
* Update DiagnosticConsoleWriter to use DataProvider protocol
* Update LinkResolver to use DataProvider protocol
* Update one test helper to use InputProvider to discover inputs
* Update tests to load inputs using test helpers
* Avoid loading same bundle twice in same test
* Avoid creating unused workspace and context in tests
* Use InMemoryDataProvider instead of custom type in test
* Avoid force try in one test
* Move additional global checks to context configuration
* Avoid copying the test bundle when the catalog content isn't modified
* Update ConvertActionIndexerTests to use InputProvider to discover inputs
* Avoid using `_legacyDataProvider` in tests
* Update tests to pass link dependency files instead of using `configureContext`
* Update final test helper to use `InputProvider` to discover inputs
Also, remove no longer used `configureContext` parameter
* Use test file system for empty test bundle
* Use test helper for setting feature flags
* Deprecate `DocumentationWorkspace`
rdar://136208312
* Update BundleDiscoveryTests to use test helpers for input discovery
* Remove unused data provider parameter from convert action initializer
* Stop conforming test file system to workspace data provider
* Deprecate `GeneratedDataProvider`
* Deprecate `PrebuiltLocalFileSystemDataProvider`
* Remove unused SymbolGraphLoader initializer
* Indicate in deprecated tests when they can be removed
* Remove out-of-date deprecation warning for already removed code
* Deprecate `DocumentationWorkspaceDataProvider`
* Deprecate `DocumentationContextDataProvider`
* Deprecate additional multi-bundle-related properties
* Add comments to deprecated tests explaining that they aren't skipped
* Update comment about why unexpected errors and turned into diagnostics and add FIXME to change this in the future
// An inner function to gather problems for errors encountered during the conversion.
71
71
//
72
-
// These problems only represent unexpected thrown errors and aren't particularly user-facing but because
73
-
// `DocumentationConverter.convert(outputConsumer:)` emits them as diagnostics we do the same here.
72
+
// These problems only represent unexpected thrown errors and aren't particularly user-facing.
73
+
// For now we emit them as diagnostics because `DocumentationConverter.convert(outputConsumer:)` (which this replaced) used to do that.
74
+
//
75
+
// FIXME: In the future we could simplify this control flow by not catching these errors and turning them into diagnostics.
76
+
// Since both error-level diagnostics and thrown errors fail the documentation build,
77
+
// the only practical different this would have is that we stop on the first unexpected error instead of processing all pages and gathering all unexpected errors.
74
78
func recordProblem(from error:Swift.Error, in problems:inout[Problem], withIdentifier identifier:String){
/// Adds new checks to be run during the global topic analysis; after a bundle has been fully registered and its topic graph has been fully built.
2558
2578
///
2559
2579
/// - Parameter newChecks: The new checks to add.
2580
+
@available(*, deprecated, message:"Use 'TopicAnalysisConfiguration.additionalChecks' instead. This deprecated API will be removed after 6.2 is released")
0 commit comments