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
The assembler doesn't respect the order of navigation.yml.
An example of this is the glossary. The glossary is defined in navigation.yml at the end of the reference section. However, in staging, you'll see the glossary in the middle of the page.
What I expect to happen
I expect the navigation/toc to be displayed in the same order that toc.yml files are included in the navigation.yml file.
Related bug
Due to the above bug, on some pages, the links to previous and next pages aren't the pages I'd expect, i.e., they don't match the navigation/TOC. For example:
The troubleshooting page is the APM Android Agent Troubleshooting page. However, that page is in the Reference content set (a completely different navigation tree).
The text was updated successfully, but these errors were encountered:
Summary
The assembler doesn't respect the order of
navigation.yml
.An example of this is the glossary. The glossary is defined in
navigation.yml
at the end of the reference section. However, in staging, you'll see the glossary in the middle of the page.What I expect to happen
I expect the navigation/toc to be displayed in the same order that
toc.yml
files are included in thenavigation.yml
file.Related bug
Due to the above bug, on some pages, the links to previous and next pages aren't the pages I'd expect, i.e., they don't match the navigation/TOC. For example:
Go to https://staging-website.elastic.co/docs/release-notes/apm/agents/android. According to the nav, the previous page is the Elastic APM Deprecations and the next page is the Elastic APM Android Agent Known Issues.
However, The previous and next links are:
The troubleshooting page is the APM Android Agent Troubleshooting page. However, that page is in the Reference content set (a completely different navigation tree).
The text was updated successfully, but these errors were encountered: