blast-hardcheese on master
Update scalafmt-core to 3.5.9 Merge pull request #1557 from s… (compare)
securitySchemescomponent and referenced it globally in the security section of my openapi config. However guardrail still generates the same Handler as before. I'm using the sbt plugin for the generation. Is basic auth support only available in the cli app or am I missing something?
HttpClient[F], by way of
FooClient.httpClient[F[_]](httpClient: Http4sClient[F], host: String = "http://localhost:1234")(implicit F: Async[F]): FooClient[F]
= Nonedefault values for optional values?
@lolgab Pardon for the delay in response! I must have missed the notification.
This isn't currently configurable, though I'm curious about your use case. Would you want to disable this in all cases, in order to make it obvious where the code needs to change if a spec changes?
The location where those
None values are interpolated is here
project/src/main/scala/dev/guardrail/CirceOverrides.scala. I'm trying to get that wrapped up soon, life has been getting in the way a bit 😅
Would you want to disable this in all cases, in order to make it obvious where the code needs to change if a spec changes?
Yes, I try to avoid default parameters since I always forget to propagate some of them and end up creating bugs.
I check if I can define that override myself, thank you very much :)
spibranch in the next few weeks, if you don't mind waiting; I can provide a working example of what you're trying to do once it's done
martijn.hoekstra.zivver: It's an unfortunate state of the MiMa checker -- I'm changing how the module system works, building towards a new minor release, but the build fails unless there's the GitHub
minor tag present in the build event...
I was thinking of trying to use the GitHub API to collect the semver tags of merged PRs, though maybe as a stopgap just disabling MiMa checking on
master would be acceptable