build(aio): fix paths to "index" pages
Content pages like `tutorial/index.md` were being mapped to `tutorial.index.json`, which meant that they could only be rendered if you browsed to `/tutorial/index`. This didn't sit well so now these pages are mapped to `tutorial.json`, which means that you browser to them via `/tutorial/` or just `/tutorial`. Fixed #15335
This commit is contained in:

committed by
Miško Hevery

parent
c9710d4fb5
commit
fc1f6efe0d
@ -10,11 +10,27 @@ describe('site App', function() {
|
||||
});
|
||||
|
||||
it('should show features text after clicking "Features"', () => {
|
||||
page.featureLink.click().then(() => {
|
||||
page.getLink('features').click().then(() => {
|
||||
expect(page.getDocViewerText()).toMatch(/Progressive web apps/i);
|
||||
});
|
||||
});
|
||||
|
||||
it('should show the tutorial index page at `/tutorial/`', () => {
|
||||
// check that we can navigate directly to the tutorial page
|
||||
page.navigateTo('tutorial/');
|
||||
expect(page.getDocViewerText()).toMatch(/Tutorial: Tour of Heroes/i);
|
||||
|
||||
// navigate to a different page
|
||||
page.getLink('features').click();
|
||||
|
||||
// check that we can navigate to the tutorial page via a link in the navigation
|
||||
const heading = page.getNavHeading(/tutorial/i);
|
||||
expect(heading.getText()).toMatch(/tutorial/i);
|
||||
heading.click();
|
||||
page.getLink('tutorial/').click();
|
||||
expect(page.getDocViewerText()).toMatch(/Tutorial: Tour of Heroes/i);
|
||||
});
|
||||
|
||||
it('should convert a doc with a code-example');
|
||||
|
||||
describe('api-docs', () => {
|
||||
|
Reference in New Issue
Block a user