Repository navigation
fix: remove warning of duplicate nextjs import - #566
Merged
Merged
Conversation
lharries
marked this pull request as draft
March 6, 2023 09:16
Contributor
|
Size Change: 0 B Total Size: 2.28 MB ℹ️ View Unchanged
|
Contributor
Author
|
@pauldambra any thoughts on whether we should keep the "return" or not? I'd suggest we default to yes as it's working with it and no need to re-initialized PostHog. I also wouldn't be expect people to be initiating the provider multiple types with different variables. |
lharries
marked this pull request as ready for review
March 6, 2023 09:24
6 of 24 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes warning of duplicate posthog import, as this occurs normally when using react strict mode