-
Notifications
You must be signed in to change notification settings - Fork 79
Add function statics and object callable properties #55
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
e291c1f
Add function statics and object callable properties
wgao19 3415f90
Update function statics and object callables
wgao19 a2208d3
Add TypeScript example for overloading callable
wgao19 faac61f
Updates on callable properties
wgao19 e103e1f
Updates on callable properties
wgao19 82f1b99
Add back the line # Read-only Types that got deleted by accident
wgao19 148fccb
Not sure how TS supports function statics
wgao19 6cc77ba
Resolve PR discussion and add function statics
wgao19 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think
[[call]]: (number) => number
is a more commonly used syntax. Flow also supports{(number) => number}
Maybe add examples for all syntaxes?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 suppose you are referring to the
$call
property syntax?Try Flow
The
$call
property syntax is deprecated and removed therefore I think we should leave that out.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.
Sorry, I should've been more clear. What I meant was include all the "syntaxes":
{ [[call]](number): number }
(explicit call property){ [[call]]: (number) => number }
(explicit call property){ (number): number }
(implicit call property).The reason why I suggested the second example is because I think it's more common in libdefs (maybe I am wrong), too. Also, I think it might be the easiest to read/notice from the three, but maybe that's just my bias.
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 see. Sorry about misreading the last comment. Will work on integrating them.