-
Notifications
You must be signed in to change notification settings - Fork 157
feat(ssr): prevent initial network request #1106
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 19d0791:
|
Same as #1090, but for Vue InstantSearch v3
c269cd8
to
19d0791
Compare
}) | ||
), | ||
scopedResults: parent.getScopedResults(), | ||
parent, |
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.
Any reason why we used not to pass parent
?
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.
only index used it, and before this PR, index was manually init/rendered in __forceWidget, meaning it didn't really do anything :)
|
||
it('accepts non-stringified results', () => { | ||
describe('hydrate', () => { | ||
it('sets _initialResults', () => { |
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 see there was a conversation to discard this test here, but it wasn't removed in the end. Any reason not to? Anything that it tests that isn't covered elsewhere?
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.
It's indeed testing some InstantSearch internals, but the main reason it stayed is that Vue InstantSearch is extending InstantSearch with a couple methods, which could in theory cause hydrate not to work correctly anymore
Same as #1090, but for Vue InstantSearch v3
fixes #1066
fixes #1062
closes algolia/instantsearch#5002