Replies: 2 comments
-
With #2062 the API will use a Jekyll generator and the API responses will be generated using a template. That will add some flexibility to add some of the missing keys. #2062 will also add product-level information to the Other comments :
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Current state of #2080 regarding this discussion.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We do a lot of templating and fixing up in the product layout (https://github.com/endoflife-date/endoflife.date/blob/master/_layouts/post.html) that doesn't reflect into the API easily. So creating a discussion to document these issues (and any more related API usecases), so we can track them and decide on how to tackle them best.
permalink
is used as default iconSlugProbably for the best if we drop the default value, and enforce
iconSlug
instead. Being explicit is better here, I think, causes less confusion.The website can hide/show columns, all of which have a default value as well.
Probably not needed in the API, but we provide a green/orange/red coloring based on some rules.
We support changelog templates, that aren't rendered. Direct links are rendered, on the other hand. (See https://endoflife.date/api/godot.json vs https://endoflife.date/api/electron.json)
The website shows relative dates, the API doesn't.
We sort releases by
sortOrder
for the website, not for the APISince the API currently only deals with release cycles, there is no information from our top level keys (such as
command
,category
,releaseImage
, orreleasePolicyLink
in the API). This will likely be a breaking change. We should probably also send amarkdown+html
version along in the API for some more interesting use-cases.Not mentioned in the API. Probably not needed.
The website links to the API via a Link header (
curl -sI https://endoflife.date/electron |grep link
) but we don't link in the other direction.We mark releases as LTS using
lts: true
, which shows up, but as we track #653, we should support LTS labels in the API as well.Release labels are templates, and the templates should be respected. They are also overwritten on a per-release basis, so that should also be implemented.
All of the above, along with a tendency for our API URLs to break is what I'd like to solve before we can move our API from Alpha->Beta or stable status.
Beta Was this translation helpful? Give feedback.
All reactions