Skip to content
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

fix: warn about invalid userToken #4605

Merged
merged 1 commit into from
Dec 9, 2020
Merged

Conversation

eunjae-lee
Copy link
Contributor

@eunjae-lee eunjae-lee commented Dec 9, 2020

Summary

This PR updates algoliasearch-helper to 3.3.4 to warn users about invalid userToken.

@eunjae-lee eunjae-lee force-pushed the fix/invalid-user-token branch from 1e97ef7 to adcbc81 Compare December 9, 2020 09:55
@codesandbox-ci
Copy link

codesandbox-ci bot commented Dec 9, 2020

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 c9916e9:

Sandbox Source
InstantSearch.js Configuration

@eunjae-lee eunjae-lee requested a review from a team December 9, 2020 10:00
@ghost ghost requested review from shortcuts and yannickcr and removed request for a team December 9, 2020 10:00
yarn.lock Outdated
@@ -2919,27 +2919,6 @@ [email protected]:
"@algolia/requester-node-http" "4.8.2"
"@algolia/transporter" "4.8.2"

algoliasearch@^3.35.1:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unfortunately you need to keep this entry in the lock file, otherwise algoliasearch-v3 won't build anymore in storybook as far as I can tell (it doesn't deal properly with the aliased module + places.js having a dependency

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why it got deleted.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yarn thinks this is the right resolution (since it deduplicates), but some other tools try to use the node_modules folder name, which is algoliasearch-v3 if it gets deduplicated

yarn.lock Outdated
dependencies:
events "^1.1.1"

"algoliasearch-v3@npm:[email protected]":
"algoliasearch-v3@npm:[email protected]", algoliasearch@^3.35.1:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Haroenv This line has changed too. Do you think I should revert it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, you should revert it too.

@eunjae-lee eunjae-lee force-pushed the fix/invalid-user-token branch from adcbc81 to c9916e9 Compare December 9, 2020 10:22
@eunjae-lee eunjae-lee merged commit 5fce769 into master Dec 9, 2020
@eunjae-lee eunjae-lee deleted the fix/invalid-user-token branch December 9, 2020 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants