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
97
98
99
100
101
102
use anyhow::Result;
use clap::ValueEnum;
use schemars::JsonSchema;
use serde::{Deserialize, Serialize};
use std::fmt::{self, Display, Formatter};
use strum::{EnumString, VariantNames};
#[derive(
Debug,
Clone,
Deserialize,
Serialize,
JsonSchema,
Copy,
Eq,
PartialEq,
EnumString,
VariantNames,
ValueEnum,
)]
#[strum(serialize_all = "snake_case")]
pub enum Operation {
#[serde(rename = "insert_after")]
InsertAfter,
#[serde(rename = "insert_before")]
InsertBefore,
#[serde(rename = "replace")]
Replace,
}
impl Operation {
pub fn as_str(&self) -> &'static str {
match self {
Operation::InsertAfter => "insert after",
Operation::InsertBefore => "insert before",
Operation::Replace => "replace",
}
}
}
impl Display for Operation {
fn fmt(&self, f: &mut Formatter<'_>) -> fmt::Result {
f.write_str(self.as_str())
}
}
#[derive(Debug, Clone, Deserialize, Serialize, JsonSchema, Eq, PartialEq, clap::Args)]
pub struct Selector {
/// The type of edit operation to perform.
///
/// - **`insert_after`** - Insert content after the complete AST node containing the anchor
/// - **`insert_before`** - Insert content before the complete AST node containing the anchor
/// - **`replace`** - Replace the entire AST node that starts with the anchor text
#[arg(value_enum)]
pub operation: Operation,
/// Text to locate in the source code as the target for the operation.
///
/// Should be a short, distinctive piece of text that uniquely identifies the location.
/// For range operations, this marks the start of the range.
/// For node operations, this should cover the start of the ast node.
///
/// Tips for Good Anchors
///
/// - **Keep anchors short but unique** - "fn main" instead of the entire function signature
/// - **Use distinctive text** - function names, keywords, or unique comments work well
/// - **Test your anchor** - if it appears multiple times, the tool will attempt to find the best placement
/// - **Whitespace doesn't matter** - anchors are whitespace-insensitive, so you can omit spaces, newlines, and indentation
///
/// # Examples
/// - `"fn main"` - Targets a function definition
/// - `"struct User"` - Targets a struct definition
/// - `"// TODO: implement"` - Targets a specific comment
/// - `"import React"` - Targets an import statement
pub anchor: String,
}
impl Selector {
pub fn operation_name(&self) -> &str {
self.operation.as_str()
}
/// Validate that the selector is properly formed
pub fn validate(&self) -> Result<(), String> {
let Self { anchor, .. } = self;
let mut errors = vec![];
if anchor.trim().is_empty() {
errors.push("- `anchor` cannot be empty");
}
// if anchor.contains('\n') {
// errors.push("- Multiline anchors are not supported. Use shorter, single-line anchors for better reliability.");
// }
if errors.is_empty() {
Ok(())
} else {
Err(errors.join("\n"))
}
}
}