How to track new products and handle name inconsistencies in endoflife.date API? #7548
Replies: 2 comments 1 reply
-
|
We have a solution for the first one: #6158. You can subscribe to this issue to get notified of new products. We try to do an announcement once every month or so. We will put an announcement on the website with an RSS feed soon. Inconsistent naming is an unsolvable problem in the absolute, but we try to solve it as much as we can:
Our Breaking Change policy/process is still being defined. Current version is at https://github.com/endoflife-date/endoflife.date/wiki/Breaking-Changes. Feedback is welcome at #7341 |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Thanks a lot for this detailed response. I wanted to know a bit more about "We have redirects, so https://endoflife.date/go takes to you https://endoflife.date/golang (and it applies to the API as well)." How do you handle these redirects, do you maintain some mapping, or do you use some algorithm to decide these redirects. |
Beta Was this translation helpful? Give feedback.
-
|
These are defined in each product as alternate_urls. A little more explanation at https://endoflife.date/contribute We compile all of these into a _redirects file which is picked up by Netlify. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using the endoflife.date API to check which libraries or tools have reached their end-of-life (EOL), and it’s been quite helpful so far.
However, I’m facing two issues:
I'm looking for suggestions on:
How others are staying up to date with new products added to the API.
Best practices for handling naming mismatches — is there a standard mapping or should I build my own?
Any help or advice would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions