Essentially, what happens seems to be that Scalariform re-formats the imports play.api.mvc.{Action, Controller} and play.api.inject.{ApplicationLifecycle,ConfigurationProvider} to include a space after the comma and the ones before inside the braces.
Then the api-first-hand generator seems to determine that those imports are missing and re-adds them.
Because of this, every sbt compile adds a pair of imports to my generated controller.
Quickly, I ended up with an import block like this:
I have found that
api-first-hand
andscalariform
can end up fighting over imports.I run Scalariform upon every compilation with the following config
Essentially, what happens seems to be that Scalariform re-formats the imports
play.api.mvc.{Action, Controller}
andplay.api.inject.{ApplicationLifecycle,ConfigurationProvider}
to include a space after the comma and the ones before inside the braces. Then theapi-first-hand
generator seems to determine that those imports are missing and re-adds them.Because of this, every
sbt compile
adds a pair of imports to my generated controller.Quickly, I ended up with an import block like this:
This change will make the generator scalariform-friendly and should resolve the above issue.