Gentle auto-import that respects Scala CLI's directives

[windymelt]

Is your feature request related to a problem? Please describe.

When I auto-import by completion in Scala Script for Scala CLI, Metals always adds import line top of my file. However, I want to keep Scala CLI directives top of the file...

e.g.

Before auto-import:

//> using scala 3.6.2

val d = FiniteDuration/* press TAB to complete! */

After auto-import:

import scala.concurrent.duration.FiniteDuration // aww〜〜
//> using scala 3.6.2

val d = FiniteDuration

Describe the solution you'd like

• Metals recognizes Scala CLI directives.
• Metals places imports below directives when auto-import.

Describe alternatives you've considered

Cut and paste

Additional context

I'm using Metals 1.4.1 on Emacs.

Search terms

autoimport auto-import import

[tgodzik]

This looks like an error when no imports are added yet.

[kasiaMarek]

Hi, I can't really reproduce your issue. It puts the import in the correct place for me.

Screen.Recording.2025-01-08.at.16.09.26.mov

Are you sure that script is correctly recognised by Metals as Scala CLI script? Meaning, either scala-cli is the build server used in your project or the script is imported as a Scala CLI script in Metals.

[dos65]

I've seen such issue when there were no \n after using directive but forgot to report it

//> using scala 3.6
val d = FiniteDuration

[kasiaMarek]

@dos65, it also seems to work for me without the \n.

[dos65]

@kasiaMarek yep, it works well on scala 3.6. my bad - the issue was on 2.13

Try this:

//> using scala 2.13
object X {
   FiniteDuration@@
}

[kubukoz]

I see directives and auto-imports keep fighting each other 😆 #4939 #6027