zed/assets/prompts/operations.md

Your task is to map a step from the conversation above to operations on symbols inside the provided source files.

Guidelines:
- There's no need to describe *what* to do, just *where* to do it.
- If creating a file, assume any subsequent updates are included at the time of creation.
- Don't create and then update a file.
- We'll create it in one shot.
- Prefer updating symbols lower in the syntax tree if possible.
- Never include operations on a parent symbol and one of its children in the same operations block.
- Never nest an operation with another operation or include CDATA or other content. All operations are leaf nodes.
- Include a description attribute for each operation with a brief, one-line description of the change to perform.
- Descriptions are required for all operations except delete.
- When generating multiple operations, ensure the descriptions are specific to each individual operation.
- Avoid referring to the location in the description. Focus on the change to be made, not the location where it's made. That's implicit with the symbol you provide.
- Don't generate multiple operations at the same location. Instead, combine them together in a single operation with a succinct combined description.

Example 1:

User:
```rs src/rectangle.rs
struct Rectangle {
    width: f64,
    height: f64,
}

impl Rectangle {
    fn new(width: f64, height: f64) -> Self {
        Rectangle { width, height }
    }
}
```

<step>Add new methods 'calculate_area' and 'calculate_perimeter' to the Rectangle struct</step>
<step>Implement the 'Display' trait for the Rectangle struct</step>

What are the operations for the step: <step>Add a new method 'calculate_area' to the Rectangle struct</step>

A (wrong):
{
  "operations": [
    {
      "kind": "AppendChild",
      "path": "src/shapes.rs",
      "symbol": "impl Rectangle",
      "description": "Add calculate_area method"
    },
    {
      "kind": "AppendChild",
      "path": "src/shapes.rs",
      "symbol": "impl Rectangle",
      "description": "Add calculate_perimeter method"
    }
  ]
}

This demonstrates what NOT to do. NEVER append multiple children at the same location.

A (corrected):
{
  "operations": [
    {
      "kind": "AppendChild",
      "path": "src/shapes.rs",
      "symbol": "impl Rectangle",
      "description": "Add calculate area and perimeter methods"
    }
  ]
}

User:
What are the operations for the step: <step>Implement the 'Display' trait for the Rectangle struct</step>

A:
{
  "operations": [
    {
      "kind": "InsertSiblingAfter",
      "path": "src/shapes.rs",
      "symbol": "impl Rectangle",
      "description": "Implement Display trait for Rectangle"
    }
  ]
}

Example 2:

User:
```rs src/user.rs
struct User {
    pub name: String,
    age: u32,
    email: String,
}

impl User {
    fn new(name: String, age: u32, email: String) -> Self {
        User { name, age, email }
    }

    pub fn print_info(&self) {
        println!("Name: {}, Age: {}, Email: {}", self.name, self.age, self.email);
    }
}
```

<step>Update the 'print_info' method to use formatted output</step>
<step>Remove the 'email' field from the User struct</step>

What are the operations for the step: <step>Update the 'print_info' method to use formatted output</step>

A:
{
  "operations": [
    {
      "kind": "Update",
      "path": "src/user.rs",
      "symbol": "impl User pub fn print_info",
      "description": "Use formatted output"
    }
  ]
}

User:
What are the operations for the step: <step>Remove the 'email' field from the User struct</step>

A:
{
  "operations": [
    {
      "kind": "Delete",
      "path": "src/user.rs",
      "symbol": "struct User email"
    }
  ]
}

Example 3:

User:
```rs src/vehicle.rs
struct Vehicle {
    make: String,
    model: String,
    year: u32,
}

impl Vehicle {
    fn new(make: String, model: String, year: u32) -> Self {
        Vehicle { make, model, year }
    }

    fn print_year(&self) {
        println!("Year: {}", self.year);
    }
}
```

<step>Add a 'use std::fmt;' statement at the beginning of the file</step>
<step>Add a new method 'start_engine' in the Vehicle impl block</step>

What are the operations for the step: <step>Add a 'use std::fmt;' statement at the beginning of the file</step>

A:
{
  "operations": [
    {
      "kind": "PrependChild",
      "path": "src/vehicle.rs",
      "description": "Add 'use std::fmt' statement"
    }
  ]
}

User:
What are the operations for the step: <step>Add a new method 'start_engine' in the Vehicle impl block</step>

A:
{
  "operations": [
    {
      "kind": "InsertSiblingAfter",
      "path": "src/vehicle.rs",
      "symbol": "impl Vehicle fn new",
      "description": "Add start_engine method"
    }
  ]
}

Example 4:

User:
```rs src/employee.rs
struct Employee {
    name: String,
    position: String,
    salary: u32,
    department: String,
}

impl Employee {
    fn new(name: String, position: String, salary: u32, department: String) -> Self {
        Employee { name, position, salary, department }
    }

    fn print_details(&self) {
        println!("Name: {}, Position: {}, Salary: {}, Department: {}",
                  self.name, self.position, self.salary, self.department);
    }

    fn give_raise(&mut self, amount: u32) {
        self.salary += amount;
    }
}
```

<step>Make salary an f32</step>

What are the operations for the step: <step>Make salary an f32</step>

A (wrong):
{
  "operations": [
    {
      "kind": "Update",
      "path": "src/employee.rs",
      "symbol": "struct Employee",
      "description": "Change the type of salary to an f32"
    },
    {
      "kind": "Update",
      "path": "src/employee.rs",
      "symbol": "struct Employee salary",
      "description": "Change the type to an f32"
    }
  ]
}

This example demonstrates what not to do. `struct Employee salary` is a child of `struct Employee`.

A (corrected):
{
  "operations": [
    {
      "kind": "Update",
      "path": "src/employee.rs",
      "symbol": "struct Employee salary",
      "description": "Change the type to an f32"
    }
  ]
}

User:
What are the correct operations for the step: <step>Remove the 'department' field and update the 'print_details' method</step>

A:
{
  "operations": [
    {
      "kind": "Delete",
      "path": "src/employee.rs",
      "symbol": "struct Employee department"
    },
    {
      "kind": "Update",
      "path": "src/employee.rs",
      "symbol": "impl Employee fn print_details",
      "description": "Don't print the 'department' field"
    }
  ]
}

Example 5:

User:
```rs src/game.rs
struct Player {
    name: String,
    health: i32,
    pub score: u32,
}

impl Player {
    pub fn new(name: String) -> Self {
        Player { name, health: 100, score: 0 }
    }
}

struct Game {
    players: Vec<Player>,
}

impl Game {
    fn new() -> Self {
        Game { players: Vec::new() }
    }
}
```

<step>Add a 'level' field to Player and update the 'new' method</step>

A:
{
  "operations": [
    {
      "kind": "InsertSiblingAfter",
      "path": "src/game.rs",
      "symbol": "struct Player pub score",
      "description": "Add level field to Player"
    },
    {
      "kind": "Update",
      "path": "src/game.rs",
      "symbol": "impl Player pub fn new",
      "description": "Initialize level in new method"
    }
  ]
}

Example 6:

User:
```rs src/config.rs
use std::collections::HashMap;

struct Config {
    settings: HashMap<String, String>,
}

impl Config {
    fn new() -> Self {
        Config { settings: HashMap::new() }
    }
}
```

<step>Add a 'load_from_file' method to Config and import necessary modules</step>

A:
{
  "operations": [
    {
      "kind": "PrependChild",
      "path": "src/config.rs",
      "description": "Import std::fs and std::io modules"
    },
    {
      "kind": "AppendChild",
      "path": "src/config.rs",
      "symbol": "impl Config",
      "description": "Add load_from_file method"
    }
  ]
}

Example 7:

User:
```rs src/database.rs
pub(crate) struct Database {
    connection: Connection,
}

impl Database {
    fn new(url: &str) -> Result<Self, Error> {
        let connection = Connection::connect(url)?;
        Ok(Database { connection })
    }

    async fn query(&self, sql: &str) -> Result<Vec<Row>, Error> {
        self.connection.query(sql, &[])
    }
}
```

<step>Add error handling to the 'query' method and create a custom error type</step>

A:
{
  "operations": [
    {
      "kind": "PrependChild",
      "path": "src/database.rs",
      "description": "Import necessary error handling modules"
    },
    {
      "kind": "InsertSiblingBefore",
      "path": "src/database.rs",
      "symbol": "pub(crate) struct Database",
      "description": "Define custom DatabaseError enum"
    },
    {
      "kind": "Update",
      "path": "src/database.rs",
      "symbol": "impl Database async fn query",
      "description": "Implement error handling in query method"
    }
  ]
}

Now generate the operations for the following step: