On Thu, Jul 14, 2022 at 4:31 PM Jason Gerlowski
wrote:
> > I think it would be best to tackle one limited area first so we can see
> it in practice both at the surface and implementation.
>
> I think that makes sense, assuming that by "tackling" you mean
> updating the API path/verb/etc and movin
Hey, thanks for chiming in David, Houston, Eric! I'm glad to get a
few affirmations on the general direction/approach of the design.
Some responses (mostly agreement) in-line.
> I strongly prefer to move our functionality to implement the new API as at
> its core/directly, and then have v1 be a
I did look over it twice now, here & there. Boy, there is a big API
surface area to Solr! Thanks for working on this huge task Jason!
I think it would be best to tackle one limited area first so we can see it
in practice both at the surface and implementation. From an implementation
perspective
As far as CORS goes, I think you are right technically…. It’s it’s own thing.
Maybe I think of it as part of API from the perspective that supporting CORS
makes it easier to integrate with the API from other systems. Kind of like
supporting Swagger etc…
> On Jul 14, 2022, at 11:35 AM, H
I have added some comments to the API spreadsheet, but really like the
direction.
Thanks for putting all of this together, it couldn't have been easy!
- Houston
On Thu, Jul 14, 2022 at 7:00 AM Jason Gerlowski
wrote:
> Hey all,
>
> Wanted to give another "plug" to the spreadsheet of proposed v2
Hey all,
Wanted to give another "plug" to the spreadsheet of proposed v2 API
changes, in case folks missed it the first time around. Please take a
look and review whenever you get a chance!
https://docs.google.com/spreadsheets/d/1HAoBBFPpSiT8mJmgNZKkZAPwfCfPvlc08m5jz3fQBpA/edit?usp=sharing
> Lo
