Corona Docs - are revision versions broken?

Solar2D General Questions/Discussion
#1

So, I was looking through the docs to see if, following the introduction of the 64-bit builds, the display.safeScreenOriginX and other safe area related APIs had been updated to accommodate Android. I looked at the revision version and realised that the APIs had just been updated today. Fantastic!

I thought to look at the build notes, which didn’t match what I expected, and then I realised that any and all revision versions on the docs were just pointing to the most recent daily build.

I haven’t paid much attention to revision versions on the docs in the past so I am not sure if this is intentional or if something is broken.

#2

We really haven’t published a new “Public” build in a while (2018.3326) and a lot has changed since then. We keep the documentation up to date and it probably makes more sense for us to reference the latest daily builds than an old public build.

Rob

#3

I fully understand that, but I thought that the reason why the revision versions were visible on the docs was so that users could see if and when these specific APIs have last been updated.

Just so that we are speaking about the same thing. I’m referring to this bit that is shown at the top of every documentation page:

Revision2019.3516

To me, that should suggest when was this particular API or function was last updated. I think that this is how it used to work in the past. Now that every page tells me that they were updated in the last daily build, I can’t track any APIs for when they are actually updated.

If this is not a mistake, but it is a feature, then I would recommend changing the word “Revision” to “Download latest build”, “Latest build” or just “Download”, or something along those lines to avoid confusion.

#4

We really haven’t published a new “Public” build in a while (2018.3326) and a lot has changed since then. We keep the documentation up to date and it probably makes more sense for us to reference the latest daily builds than an old public build.

Rob

#5

I fully understand that, but I thought that the reason why the revision versions were visible on the docs was so that users could see if and when these specific APIs have last been updated.

Just so that we are speaking about the same thing. I’m referring to this bit that is shown at the top of every documentation page:

Revision2019.3516

To me, that should suggest when was this particular API or function was last updated. I think that this is how it used to work in the past. Now that every page tells me that they were updated in the last daily build, I can’t track any APIs for when they are actually updated.

If this is not a mistake, but it is a feature, then I would recommend changing the word “Revision” to “Download latest build”, “Latest build” or just “Download”, or something along those lines to avoid confusion.