-
Notifications
You must be signed in to change notification settings - Fork 28
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 typo for isJsxFragment. #17
Conversation
isJsxFramgment -> isJsxFragment
Any idea on the ci failure? Looks to be an issue with publishing to coveralls. |
typeguard/node.ts
Outdated
@@ -357,7 +357,7 @@ export function isJsxExpression(node: ts.Node): node is ts.JsxExpression { | |||
return node.kind === ts.SyntaxKind.JsxExpression; | |||
} | |||
|
|||
export function isJsxFramgment(node: ts.Node): node is ts.JsxFragment { | |||
export function isJsxFragment(node: ts.Node): node is ts.JsxFragment { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather keep the misnamed function around to avoid a breaking change. It can just defer to the new function and is marked as @deprecated
in jsdoc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a really good idea. I will make that change.
Thanks @dmiller9911 |
This change is released in v2.13.1 |
isJsxFramgment -> isJsxFragment