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
ENSIME proposals (refined after Scala Sphere discussions) #613
Conversation
@fommil, don't have permission to check my name, so you'll have to do it for me. ;) |
Same for me ;-) |
@wpopielarski good point! @sschaef are you happy to advise on the scala-refactoring project? (or the debugging one?) |
sure, but for debugging @wpopielarski is the expert, not me ;) |
@sschaef yeah, that's what I was thinking. Will add your name to the scala-refactoring one |
Sure, please check for me as I don't have write access |
awesome! Cross team collaboration FTW 😄 |
@julienrf this is ready for merge |
Thanks @fommil, I’ll review this ASAP! |
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.
Looks good excepted the weird markup :)
gsoc/2017.md
Outdated
method" or "organise imports", but IntelliJ have their own | ||
implementation. | ||
|
||
Within the past year the =scala.meta= / scalafix projects have become |
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.
Why these =
around “scala.meta”?
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.
org-mode, should be backticks for markdown
Thanks! |
Should this be "Scala Sphere", not "Scala World"? |
@propensive I am always doing that |
I've taken the liberty of adding the following as advisors (or supervisors in some cases). Please confirm if you're ok with this: