-
Notifications
You must be signed in to change notification settings - Fork 46
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
feat: support a few domains (404) #284
feat: support a few domains (404) #284
Conversation
288f6d0
to
d3a0147
Compare
d3a0147
to
4702869
Compare
ed612be
to
66b0652
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pls write E2E tests for this
done |
e2e/spec/404.spec.e2e.ts
Outdated
|
||
Scenario('Renders (SSR) global 404 page for non-existing ILC route for domain "127.0.0.1:8233"', (I, common: common) => { | ||
I.amOnPage(common.url.localhostAsIPv4 + '/nonexistent-path'); | ||
I.waitForText(common.text404NotFound, 10, 'body > div#navbar'); // for "127.0.0.1:8233" inside of navbar will be rendered 404 fragment, like in body |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this test checks nothing... We need to validate that "other" 404 page can be rendered for custom domain.
c5f6207
to
0a467e7
Compare
33a30ee
to
15c0ec0
Compare
15c0ec0
to
8b24f68
Compare
No description provided.