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 Segment's analytics.page optional arguments. #32061

Merged
merged 1 commit into from Jan 16, 2019

Conversation

Projects
None yet
3 participants
@davidgomes
Copy link
Contributor

davidgomes commented Jan 11, 2019

The name and category arguments should be optional as per the documentation linked below.

  • Use a meaningful title for the pull request. Include the name of the package modified.
  • Test the change in your own code. (Compile and run.)
  • Add or edit tests to reflect the change. (Run with npm test.)
  • Follow the advice from the readme.
  • Avoid common mistakes.
  • Run npm run lint package-name (or tsc if no tslint.json is present).

If changing an existing definition:

@typescript-bot

This comment has been minimized.

Copy link

typescript-bot commented Jan 11, 2019

@davidgomes Thank you for submitting this PR!

🔔 @fongandrew - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

@typescript-bot typescript-bot moved this from Waiting for Reviewers to Review in Pull Request Status Board Jan 16, 2019

@typescript-bot

This comment has been minimized.

Copy link

typescript-bot commented Jan 16, 2019

After 5 days, no one has reviewed the PR 😞. A maintainer will be reviewing the PR in the next few days and will either merge it or request revisions. Thank you for your patience!

@DanielRosenwasser DanielRosenwasser merged commit d19b9e4 into DefinitelyTyped:master Jan 16, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment