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

Failing hooks test to code against #165

Merged
merged 3 commits into from
Oct 19, 2020
Merged

Failing hooks test to code against #165

merged 3 commits into from
Oct 19, 2020

Conversation

tizmagik
Copy link
Collaborator

@tizmagik tizmagik commented Oct 13, 2020

An initial PR to introduce some failing tests (skipped) to code against for #138

Copy link
Collaborator

@bgergen bgergen left a comment

Choose a reason for hiding this comment

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

This looks great! Some interesting things to think about in the todos re: the API design, but this definitely feels like enough to get started coding against.

};

const Page = () => {
useTracking({ page: 'Page' });
Copy link
Collaborator

Choose a reason for hiding this comment

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

How is this different from the 2 tests above this one, where it does dispatch a pageview event?

Copy link
Collaborator Author

@tizmagik tizmagik Oct 19, 2020

Choose a reason for hiding this comment

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

Ah good catch, I think this was a bad copy pasta, the process function should no-op to match up with the corresponding e2e test.

@tizmagik tizmagik merged commit 38a8962 into master Oct 19, 2020
@tizmagik tizmagik deleted the hooks-tests branch October 19, 2020 21:09
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