Normalize version numbers in API calls about endoflife.date HOT 2 OPEN

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

from endoflife.date.

Hi @Cohen-Carlisle, I don't know if it applies to react, but we try to follow how particular releases are supported by the product vendor. So this type of inconsistency can happen if the vendor changed the way the product is supported (for example if the support was in the past on major, but is now on major.minor).

Having said that, for React I can think of two cases:

1. Either the support was always on major.minor : in this case the product must be updated to reflect that and it will fix the issue you are facing.
2. Or it changed over time, and in this case the product is properly documented. So this means we need to do something in the API to accommodate your request.

For the second point, I think it would be hard to specialize the documented releases from major to major.minor. Generalizing major.minor to just major may be a bit simpler, but this must be done only for the latest major.minor. Another solution could be to respond to each specific version (major.minor.patch), but this would require to have an up-to-date list of all versions.

So I agree this would be nice to "normalize" the version number, but except if it's an error in the way the product is documented (case 1) it won't be easy to implement.

from endoflife.date.