-
-
Notifications
You must be signed in to change notification settings - Fork 432
Scalafmt support #308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Scalafmt support #308
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3fe5913
add scalafmt module, that formats all sources files on every run
rockjam 73f04d9
scalafmt worker that internally chaches reformatted files
rockjam ac36673
move jvm process call to helper method
rockjam 0da6bcd
use scala 2.12.4 to resolve scalafmt deps; check for config file exis…
rockjam 34587b9
make a scalafmt worker a singleton
rockjam fef9051
add tests for scalafmt module
rockjam c6be48d
add reformatAll command
rockjam bfbbb6d
tests for reformatAll command
rockjam a58982e
add docs about scalafmt support
rockjam File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
make a scalafmt worker a singleton
- Loading branch information
commit 34587b991a54b387de6868276cf0b26efbdce8d6
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It wasn't immediately clear that worker must live in a separate module to be a single one in a build.
Also, I copy-pasted
extends ExternalModulefrom scala and scalajs workers. Why should it be anExternalModule, not just aModule?When I tried
extends Modulecomplilation failed with:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rockjam being an
ExternalModuleallows a taskmyTaskto be run viamill.scalalib.scalafmt.ScalafmtWorkerModule/myTask. NormalModuleobjects must be defined in thebuild.scfile and be run via their object selector from the root ofbuild.sc.If you want to let people run ScalaFmt without needing to extend anything, you could make a task in the
ExternalModulethat lets people run e.g.mill.scalalib.scalafmt.ScalafmtWorkerModule/fmt __.sourcesto format thesourcesof all theirScalaModules. See how themill.scalalib.PublishModule/publishAllcommand works as an example.As for being separate Mill submodules, we only needed to put things like
ScalaWorker/ScalaJSWorkerin there because we needed code that runs with some heavyweight dependencies on the classpath that might collide (e.g. different Scala.js versions): the dependencies are isolated within a classloader and interacted with via reflection. If you don't have any heavyweight dependencies, or you do but you can just interact with them directly via reflection/subprocesses, then there's no need to isolate them in a separate Mill build module