Skip to content
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

Merged
merged 3 commits into from
Mar 19, 2018
Merged

Conversation

raboof
Copy link
Member

@raboof raboof commented Mar 16, 2018

Refs #82

"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))
Copy link
Member

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
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

@2m 2m left a 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.

@2m 2m merged commit 2e95b8a into master Mar 19, 2018
@2m 2m deleted the scalaFlatPackagesByDefault branch March 19, 2018 10:37
@2m 2m mentioned this pull request Mar 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants