sullis on master
Update mockito-scala, ... to 1.… (compare)
blast-hardcheese on master
Update scalameta, semanticdb-sc… Merge pull request #1378 from s… (compare)
blast-hardcheese on master
Update mockito-scala, ... to 1.… Merge pull request #1377 from s… (compare)
CLICommonis much more clean. Previously it was a mess because
parseArgswas incorrectly part of
CoreTerms, so we had a circular reference thing that mucked everything up. guardrail-dev/guardrail#1213
release-drafterconfiguration per module, accumulating PRs that impact that module, and when that release is cut it'll just run the release for that one module. release-drafter/release-drafter#935
core, with a
provided-scope dependency on the different modules. That way the interfaces stay the same, but when they change in
corethat'll also trigger a republish of the main guardrail dep.
scala-http4s, it'll just release that one module. The next time a depending module is released, it'll pick up the most recent version of that module from the git tags and use that published artifact
on: releasetriggers to be filtered in any way, so my initial assumption about that being clean are also invalid. Gonna have to refactor that to avoid spam in the Actions tab)
dependsOnversions ended up pulling their
git descversion numbers instead of real versions.
Hello, is guardrail supposed to support specifying multiple response types?
As in https://swagger.io/docs/specification/describing-responses/#media-types
content: application/json: schema: $ref: '#/components/schemas/ArrayOfUsers' application/xml: schema: $ref: '#/components/schemas/ArrayOfUsers'
When I did that with guardrail, the generated code contained only the last defined
So an interesting side effect of the module system that I hadn't considered, when a release-drafter release is cut, the tag is minted immediately. This has the effect of all subsequent runs compiling against the ABI exposed by the compiled modules in the source trees, but publishing POMs that refer to the tagged module versions.
The implications of this are that so long as you click release on the various drafts in the reverse-depends order, you can just release everything at once, and as the modules trickle up to bintray, they'll all be pointing at the right versions of stuff
sbt:guardrail-sample-http4s> compile Missing dependency: guardrail-scala-http4s [error] (Compile / guardrail) dev.guardrail.sbt.CodegenFailedException [error] Total time: 0 s, completed Oct 14, 2021 6:31:52 PM
If I then stick
libraryDependencies += "dev.guardrail" %% "guardrail-scala-http4s" % "0.65.3-8-ga447b33-SNAPSHOT"
project/plugins.sbt, it runs and generates sources, compiling successfully