-
Notifications
You must be signed in to change notification settings - Fork 530
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
chore(examples): update demos to use instantsearch from repo #4030
Conversation
Seems good, but should we not do that for all examples? Downside is now that it won’t work standalone in csb anymore. I’d really rather have a purpose-built example for the tests |
Mmm, I don't think we'll run some tests on them (maybe on the new media demo but it is not merged yet #3915) but I can update them to stay consistent 🙂
Is it a problem? I never saw these demos used in csb. |
I don't remember if we agreed to run it on the actual example. I thought the reasoning was that we should create a minimal example (e.g. no Google Fonts, no image header to speed up the page load). We could add these minimal examples in the WDYT? |
Yes, but it was planned to do this in a second time since already having a running test suite on the existing examples was way faster to set up and already bring us a lot of value to improve InstantSearch reliability.
New examples (like the e-commerce demo) are already not runnable in CodeSansbox anyway, no? Or I am missing something here? |
Ok, I missed that CodeSandbox runs the parcel build. Still not convinced that keeping this "feature" worth the hassle tho. |
As we decided IRL last week, to go faster we'll use the existing demos for now and see in the future if some dedicated demos are required. |
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.
Netlify is still stuck though.
Summary
To improve InstantSearch releases reliability we plan to add some End-2-End tests in addition to our existing unit test suite.
Since we'll use the e-commerce demo to run our tests then we need to update it to use the
instantsearch.js
build from the current branch.To achieve this, this PR makes the following changes:
instantsearch.js
from dependenciesinstantsearch.js
to use the build in the parent directory (using Parcel aliases and TypeScript path mapping)website:build
command to buildinstantsearch
before the demos