add compatibility with compiler option -no-indent - #359
Conversation
|
ran ci locally and latest commit seemed to fix |
|
@keynmol is there an easy way to see the generated code from the tests? I've got a couple of bugs in the refactor and AFAICT it gets cleaned up after the CI run so i can't easily pinpoint the issue. A couple of the |
|
@jbwheatley You can just do Alternatively, you can see where the files are generated: Another alternative is you can wait until I'm done with #360 which checks-in the generated bindings into the stable locations in the repo, to make it |
|
Plugin tests are a bit wonkier, as SBT scripted tests are opaque and sandboxed. |
|
thanks for the help, managed to fix things pretty quickly after that. I broke out some util functions as suggested, I think it definitely helps readability and uniformity :) |
…, fix missing space
| if hasUnions then l(s"export _root_.${packageName}.unions.*") | ||
| if hasAnyEnums then l(s"export _root_.${packageName}.enumerations.*") | ||
| objectBlock(l)("object types") { | ||
| nest { |
There was a problem hiding this comment.
I think this extra nesting is unnecessary (no need to fix, I will address myself after merging this)
see #353
This PR adds support for projects that use the compiler option
-no-indent. As part of the sbt plugin it checks whether the build has the -no-indent compiler option set and swap whitespace for braces accordingly.Also adds a CLI option for generating sources with braces.