+1 (binding)
Thanks for your effort, Jason.
Smoke test passed and I did some manual testing w/ scaling etc. and
everything seems to work as expected.
I'd also like to share that I did run into issues when running with 'kind'
version 0.9. Upgrading it to 0.14 fixed the issue, but it took a while
Yes that's true, if you only want to generate clients and not the server
then you can definitely have an easier time of things.
On Tue, 9 Aug 2022 at 14:21, Jason Gerlowski wrote:
> Thanks for the insight Colvin! Spec-driving-the-code sounds appealing
> in a lot of ways (I'd love to have default
Thanks for the insight Colvin! Spec-driving-the-code sounds appealing
in a lot of ways (I'd love to have defaults handled uniformly across
Solr, for instance), but I think Jan's right that it's probably
infeasible for Solr.
And "point taken" about expecting some issues with the tooling!
Best,
Ja
I have recent experience from a SpringBoot / Kotlin application where we use
code-first annotation driven OpenAPI definition. I think that will be the only
feasible way for Solr.
The sweet thing about that approach is that the OpenAPI definitions and
documentation is all done inline with the co
I spent the first few months of this year adopting OpenAPI 3 spec in our
product, which has a fairly large API.
We previously generated a Swagger 1.0 spec from our Java code, now we're
generating our POJOs and JAX-RS endpoints from the OA3 spec.
Aside from needing to get off outdated Swagger 1 to
Makes sense to explore at this point to figure out best order of development.
And with the door open to slightly adapt some URL patterns in v2, should it be
required, it's less likely that roadblocks would derail the entire effort.
Jan
> 8. aug. 2022 kl. 18:10 skrev Jason Gerlowski :
>
> Hey a
