Rename FixIt.Change.textualReplacement to replaceText(range:with:in:)

Rename according to the discussion. Additionally, only require a Syntax node
(not a SourceFileSyntax) as the place we're rewriting from.

Author: DougGregor

Release Notes/602.md

@@ -2,16 +2,24 @@
 
 ## New APIs
 
-- `DiagnosticMessage` has a new optional property, `category`, that providesa category name and documentation URL for a diagnostic.
-  - Description: Tools often have many different diagnostics. Diagnostic categories allow tools to group several diagnostics together with documentation that can help users understand what the diagnostics mean and how to address them. This API allows diagnostics to provide this category information. The diagnostic renderer will provide the category at the end of the diagnostic message in the form `[#CategoryName]`, and can print categories as "footnotes" with its `categoryFootnotes` method.
-  - Pull Request: https://github.com/swiftlang/swift-syntax/pull/2981
-  - Migration steps: None required. The new `category` property has optional type, and there is a default implementation that returns `nil`. Types that conform to `DiagnosticMessage` can choose to implement this property and provide a category when appropriate.
-
 - `SwiftLexicalLookup` - A new Swift unqualified lookup library
   - Description: The library provides a new Swift unqualified lookup implementation detached from the compiler and accessible to outside clients. The query is stateless and can be directly run on swift-syntax syntax tree, with any syntax node functioning as an entry point. It produces an enum-based data structure as a result that partitions collected names based on the lexical scope of introduction. 
   - Pull Request: https://github.com/swiftlang/swift-syntax/pull/2952
   - Notes: The library follows the behavior of the compiler implementation with some minor differences, such as a different way of handling dollar identifiers `$x` and generic parameters inside extensions. Furthermore, in the future, once the compiler adopts `SwiftLexicalLookup` and it becomes the canonical implementation, results produced by the query will be guaranteed to be correct.
 
+- `DiagnosticMessage` has a new optional property, `category`, that provides a category name and documentation URL for a diagnostic.
+  - Description: Tools often have many different diagnostics. Diagnostic categories allow tools to group several diagnostics together with documentation that can help users understand what the diagnostics mean and how to address them. This API allows diagnostics to provide this category information. The diagnostic renderer will provide the category at the end of the diagnostic message in the form `[#CategoryName]`, and can print categories as "footnotes" with its `categoryFootnotes` method.
+  - Pull Request: https://github.com/swiftlang/swift-syntax/pull/2981
+  - Migration steps: None required. The new `category` property has optional type, and there is a default implementation that returns `nil`. Types that conform to `DiagnosticMessage` can choose to implement this property and provide a category when appropriate.
+
+- `FixIt.Change` has a new case `replaceText` that performs a textual replacement of a range of text with another string.
+  - Description: The other `FixIt.Change` cases provide structured
+    modifications to syntax trees, such as replacing specific notes. Some
+    clients provide Fix-Its that don't fit well into this structured model. The
+    `replaceText` case makes it possible for such clients to express Fix-Its.
+  - Pull request: https://github.com/swiftlang/swift-syntax/pull/3030
+  - Migration stems: None required.
+
 ## API Behavior Changes
 
 ## Deprecations

Sources/SwiftCompilerPluginMessageHandling/Diagnostics.swift

@@ -150,12 +150,12 @@ extension PluginMessage.Diagnostic {
           case .replaceChild(let replaceChildData):
             range = sourceManager.range(replaceChildData.replacementRange, in: replaceChildData.parent)
             text = replaceChildData.newChild.description
-          case .textualReplacement(
-            replacementRange: let replacementRange,
-            sourceFile: let sourceFile,
-            newText: let newText
+          case .replaceText(
+            range: let replacementRange,
+            with: let newText,
+            in: let syntax
           ):
-            range = sourceManager.range(replacementRange, in: sourceFile)
+            range = sourceManager.range(replacementRange, in: syntax)
             text = newText
           #if RESILIENT_LIBRARIES
           @unknown default:

Sources/SwiftDiagnostics/FixIt.swift

@@ -77,14 +77,14 @@ public struct FixIt: Sendable {
     case replaceTrailingTrivia(token: TokenSyntax, newTrivia: Trivia)
     /// Replace the child node of the given parent node at the given replacement range with the given new child node
     case replaceChild(data: any ReplacingChildData)
-    /// Replace the text within the given range in a source file with new text.
+    /// Replace the text within the given range in a syntax node with new text.
     ///
     /// Generally, one should use other cases to replace specific syntax nodes
     /// or trivia, because it more easily leads to a correct result. However,
     /// this case provides a fallback for textual replacement that ignores
     /// syntactic structure. After applying a textual replacement, there is no
     /// way to get back to a syntax tree without reparsing.
-    case textualReplacement(replacementRange: Range<AbsolutePosition>, sourceFile: SourceFileSyntax, newText: String)
+    case replaceText(range: Range<AbsolutePosition>, with: String, in: Syntax)
   }
 
   /// A description of what this Fix-It performs.
@@ -166,7 +166,7 @@ private extension FixIt.Change {
         replacement: replacingChildData.newChild.description
       )
 
-    case .textualReplacement(replacementRange: let replacementRange, sourceFile: _, newText: let newText):
+    case .replaceText(range: let replacementRange, with: let newText, in: _):
       return SourceEdit(range: replacementRange, replacement: newText)
     }
   }

Sources/SwiftSyntaxMacrosGenericTestSupport/Assertions.swift

@@ -633,9 +633,9 @@ fileprivate extension FixIt.Change {
         replacement: replacingChildData.newChild.description
       )
 
-    case .textualReplacement(replacementRange: let range, sourceFile: let sourceFile, newText: let newText):
-      let start = expansionContext.position(of: range.lowerBound, anchoredAt: sourceFile)
-      let end = expansionContext.position(of: range.upperBound, anchoredAt: sourceFile)
+    case .replaceText(range: let range, with: let newText, in: let syntax):
+      let start = expansionContext.position(of: range.lowerBound, anchoredAt: syntax)
+      let end = expansionContext.position(of: range.upperBound, anchoredAt: syntax)
       return SourceEdit(range: start..<end, replacement: newText)
     }
   }

Tests/SwiftDiagnosticsTest/FixItTests.swift

@@ -55,7 +55,11 @@ final class FixItTests: XCTestCase {
     let change = FixIt(
       message: SimpleFixItMessage(message: "fix it please"),
       changes: [
-        .textualReplacement(replacementRange: five..<fifteen, sourceFile: "func myFunction() { }", newText: "yours")
+        .replaceText(
+          range: five..<fifteen,
+          with: "yours",
+          in: Syntax("func myFunction() { }" as SourceFileSyntax)
+        )
       ]
     )
     XCTAssertEqual(change.edits.count, 1)