-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
$Call with arguments has confusing documentation #149
Comments
Oh! Is this what it should be?
|
Yes, it's a typo in docs, PR is welcomed! Regarding the OP issue, it's impossible to implement the same behavior using TS as it's used in Flow at the moment, so we are using a simpler alternative. Maybe the solution here is to change the name/description so it's less confusing. Feel free to suggest something better and open a PR. I'll be happy to help and the community will benefit from it. |
See piotrwitek#149 . I don't know if this patch should close that issue, though.
Ah, great. I just edited on the GitHub site: #154
Hmm, I'm not sure. I guess it's fine. I was converting from Flow so I ended up just going with the built-in You may be aware already but |
See #149 . I don't know if this patch should close that issue, though.
Thanks for the typo fix! I think adding the comment and linking to build-in |
Sure. I proposed this #155 |
I think this can be closed now. |
Description
The documentation for
$Call
is unclear:What is
returnOfIncrement
and where does it come from?I read #21 but I still don't understand. Thanks for your help.
Steps to Reproduce
$Call
where$Call
originally was given two argumentsExpected behavior
The docs should provide a more clear example of how to convert old Flow style usage of
$Call
with arguments.Suggested solution(s)
Provide an example of working TypeScript code in the docs
Project Dependencies
tsconfig.json
Environment (optional)
The text was updated successfully, but these errors were encountered: