Unused import

[MasseGuillaume]

I have "-Xfatal-warnings", "-Ywarn-unused-import", in my scalacOptions

I cannot use twirl

import play.twirl.api._
import play.twirl.api.TemplateMagic._

class error extends BaseScalaTemplate[play.twirl.api.HtmlFormat.Appendable,Format[play.twirl.api.HtmlFormat.Appendable]](play.twirl.api$

[kusamakura]

One workaround I did was to add a dummy line somewhere that uses both imports:
@if(List.empty[Txt]){}

(Uses play.twirl.api.Txt and play.twirl.api.TemplateMagic.iterableToBoolean)

[Pyppe]

Any chance for this to get fixed? Or maybe a pointer (for a person such as myself who hasn't worked with sbt plugins) where to look at in order to get this fixed?

[schmitch]

You can set TwirlKeys.templateImports := Seq() which will actually remove all the imports. However you should re add the necessary onces.

[bfil]

Customizing the templateImports doesn't really fix the issue when you have different templates needing different imports. Unless I'm missing something?

[marcospereira]

@bfil if you set the value of TwirlKeys.templateImportsto an empty Seq like @schmitch suggested, then it will solve the issue, since no imports will be automatically added to the views. You can then re-add the necessary imports to each view.

[bfil]

I was thinking: if I have template1.scala.html using @Html and template2.scala.html using @Txt, then If I add both to the SBT settings template1 will say unused import on Txt and template2 will say unused import on Html, cause it's a global setting.

I guess the suggestion is removing them all from the SBT settings and adding the import line within the templates themselves.

[steinybot]

This is similar to playframework/playframework#7382 although far more painful to workaround.

[mckinley-olsen-oc]

@marcospereira which import would I need to add in order to use the traditional syntax of routes.Assets.versioned("someFile.js")?
edit: got it figured out; no import, just need to refer directly to controllers.routes.Assets; there must be some magic going on I don't quite understand. Anyway, happy to be failing on warnings now

[iaco86]

This becomes even more painful when using gradle - no workaround to be found there :(

[robinspollak]

We are also experiencing this. Any chance of a fix?

[marcospereira]

here must be some magic going on I don't quite understand

@mckinley-olsen-oc there are some default imports made for all the templates. That is why you can use routes.Assets without writing an import by yourself.