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 issues with Node.isOptional() typings #374

Merged
merged 1 commit into from
May 2, 2022
Merged

Conversation

zsakowitz
Copy link
Contributor

Currently, Node.isOptional is a function returning a boolean, but the typings show it as a property, not a method. Changing it to a method would help many TypeScript users, and I'm running into issues using this function myself.

Currently, Node.isOptional is a function returning a boolean, but the typings show it as a property, not a method. Changing it to a method would help many TypeScript users, and I'm running into issues using this function myself.
Copy link
Contributor

@pdubroy pdubroy left a comment

Choose a reason for hiding this comment

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

Thanks!

@pdubroy pdubroy merged commit d3631fc into ohmjs:master May 2, 2022
@pdubroy
Copy link
Contributor

pdubroy commented May 2, 2022

I've just published v16.3.3 containing this fix.

@zsakowitz zsakowitz deleted the patch-1 branch May 2, 2022 15:09
@zsakowitz zsakowitz restored the patch-1 branch May 2, 2022 15:09
@zsakowitz
Copy link
Contributor Author

Thank you!

@zsakowitz
Copy link
Contributor Author

I just tried to download the latest version (v16.3.3) and it doesn't have the fix. Can you double-check that you've uploaded it?

@pdubroy
Copy link
Contributor

pdubroy commented May 2, 2022

My bad. I forgot that this file is generated from index.d.ts.template — so as soon as I ran the release, it overwrote the changes. I just landed a proper fix and did a new release (v16.3.4).

Thanks for pointing out the mistake!

@zsakowitz
Copy link
Contributor Author

Oops. Sorry about that! Thanks for patching it properly and being so quick to respond.

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.

None yet

2 participants