You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to search for "createWorldTerrainAsync" in the search bar gives no results.
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.

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.
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.
The text was updated successfully, but these errors were encountered: