"convert to use" action - error when parameters are out of order

[CloserToTheCenter]

Issue with "convert to use" refactoring action.

When using parameter tags to call a function with "out-of-order" parameters, the refactoring action produces invalid code.

fn refactors_okay(items) {
  list.fold(items, from: 0, with: fn (total, item) { 
    total + item 
  })
}

fn buggy(items) {
  // now the starting point "0" comes first
  list.fold(0, over: items, with: fn (total, item) {
    total + item
  })
}

// the above is valid gleam code but refactors to this invalid code
fn buggy_refactor(items) {
  use total, item <- list.fold(0) // missing the "items" parameter
  total + item
}

I organically arrived at out of order parameters because I had

my_object.long_involved_constructor()
|> list.fold(over: items, with: fn (a, b) { todo })

// then I used the "inline pipe" action
list.fold(my_object.long_involved_constructor(), over: items, with: fn (a, b) { todo })

// then I used the "convert to use" action
use a, b <- list.fold(my_object.long_involved_constructor())
todo

// but now the "items" variable has gone missing

Gleam version 1.9.1

[lpil]

Thank you!

To make sure I understand, is the situation that you ran the code action on some invalid code?

[CloserToTheCenter]

Run the code action on valid code and it outputs invalid, broken code.

[lpil]

AH! Thank you