-
Notifications
You must be signed in to change notification settings - Fork 124
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
Use flat_package for scala codegen by default #106
Conversation
project/ReflectiveCodeGen.scala
Outdated
"single_line_to_string" -> false).collect { case (settingName, v) if v => settingName } | ||
|
||
MutableGeneratorAccess(adapted.setUnderlying _, (generator, settings)) | ||
MutableGeneratorAccess(adapted.setUnderlying _, (JvmGenerator(s"mutable", adapted), codeGeneratorSettings)) |
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.
Not used interpolation.
// that are more consistent between Scala and Java. | ||
// Because the interop tests generate both Scala and Java code, however, here we disable this | ||
// option to avoid name clashes in the generated classes: | ||
(codeGeneratorSettings in Compile) := Seq.empty |
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.
Maybe use (codeGeneratorSettings in Compile).value.filterNot(_ == "flat_package")
in case we have other settings by default?
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.
👍 not super nice to have this stringly-typed but most flexible and not really worth adding infrastructure for I suppose.
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.
LGTM with a couple of nitpicks.
Refs #82