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 nosto-js-sdk usage #207

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Fix nosto-js-sdk usage #207

merged 1 commit into from
Nov 6, 2024

Conversation

timowestnosto
Copy link
Contributor

No description provided.

@timowestnosto timowestnosto force-pushed the nostojs-fixes branch 2 times, most recently from 43cd0ce to d2eb210 Compare November 5, 2024 18:11
@@ -20,6 +20,7 @@ function RecommendationComponentWrapper(props: {
}

function injectCampaigns(data: CampaignData) {
// @ts-expect-error not defined
if (!window.nostojs) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we use global namespace definition to overcome this and avoid ts-expect-error comment?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That would make it global, we have the nostojs import from the nosto-js library which should take care of it, but isNostoLoaded() didn't work

Copy link
Contributor

Choose a reason for hiding this comment

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

Let's come back to this later. Not a blocker.

@timowestnosto timowestnosto merged commit 44088b0 into feat/useNostoJsSdk Nov 6, 2024
1 check passed
@timowestnosto timowestnosto deleted the nostojs-fixes branch November 6, 2024 07:37
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