Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cesium reference docs host old versions of the documentation in certain pages. #11303

Open
ethanchristensen01 opened this issue May 23, 2023 · 2 comments · Fixed by #11311
Open

Comments

@ethanchristensen01
Copy link

I was searching for "cesium docs createWorldTerrain" in a search engine and came across this: https://cesium.com/learn/cesiumjs/ref-doc/createWorldTerrain.html

Trying to search for "createWorldTerrainAsync" in the search bar gives no results.
Documentation for createWorldTerrain with "createWo" in the search bar. There are two results, but "createWorldTerrainAsync" is not one of them.

After a bit of sleuthing, it seems like this page specifically uses an older version of the documentation. Navigating to the index, you can find createWorldTerrainAsync, which navigates to the Global members page. Searching here for "createWorldTerrainAsync" does give a result.

Documentation for createWorldTerrainAsync, which is part of a bigger page. "createWo" is in the search bar, and this time, there are four results, including createWorldTerrainAsync.

With this result, you can see different sections for packages/engine and packages/widgets. This makes me think there are different versions of the documentation available on different pages, which is probably a bug. There may be other pages that have this same issue.

@ethanchristensen01
Copy link
Author

Also worth noting is that createWorldTerrain is not marked as deprecated in either page.

@ggetz
Copy link
Contributor

ggetz commented May 24, 2023

Thanks for the report @ethanchristensen01! createWorldTerrain should indeed be marked as deprecated.

The older files are not explicitly cleaned up as part of our website deployment process, but are usually automatically clean up after a set amount of time. We'll take a look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants