search

google / deps.dev

Resources for the deps.dev API
https://deps.dev
Apache License 2.0
242 stars 18 forks source link

Compatibility v3 - v3alpha #76

Closed edoardottt closed 5 months ago

edoardottt commented 5 months ago

I'm the author of depsdev client and I'm trying to give people the opportunity to choose between 3 and v3alpha. I'm trying to understand how you treat the development of these two versions. Is v3alpha an "extension" of v3 API?

  1. v3alpha just add new response items wrt v3?
  2. There could be input items for v3alpha not allowed for v3?
  3. There could exist an item in the responses that is added in v3 and not in v3alpha?

Based on your responsed I have to understand if I have to treat v3alpha as an extension of v3 for future features or as 2 separate branches of the same project. Thanks

adg commented 5 months ago

v3alpha provides no stability guarantees and so users of v3alpha should be very aware that what they depend on is not stable.

IMO, you should maintain the v3 and v3alpha clients as separate packages. They are separate API endpoints (and proto files), after all.

edoardottt commented 5 months ago

thank you so much @adg