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.

Sign up for GitHub

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

Jump to bottom

feat(typescript): support BigInt #5546

Merged
merged 3 commits into from Nov 27, 2018
Merged

feat(typescript): support BigInt #5546

merged 3 commits into from Nov 27, 2018

Conversation

ikatyang
Copy link
Member

@ikatyang ikatyang commented Nov 25, 2018 •
edited

Fixes #5545

  • I’ve added tests to confirm my change works.
  • (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory)
  • I’ve read the contributing guidelines.

✨Try the playground for this PR✨

@ikatyang ikatyang added the status:wip Pull requests that are a work in progress and should not be merged label Nov 25, 2018
@ikatyang ikatyang added this to the 1.15.3 milestone Nov 25, 2018
@ikatyang ikatyang removed the status:wip Pull requests that are a work in progress and should not be merged label Nov 26, 2018
@ikatyang ikatyang merged commit 05ad885 into prettier:master Nov 27, 2018
@ikatyang ikatyang deleted the feat/typescript/support-big-int branch November 27, 2018 08:53
@lock lock bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Feb 25, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@JamesHenry JamesHenry JamesHenry approved these changes

@j-f1 j-f1 j-f1 approved these changes

Assignees
No one assigned
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting.
Projects
None yet
Milestone
1.15.3
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@ikatyang @JamesHenry @j-f1