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

Split function annotation into argument and return type annotations #202

Open
wants to merge 8 commits into
base: net211
Choose a base branch
from

Conversation

mcon
Copy link
Contributor

@mcon mcon commented Nov 15, 2020

As previously suggested, have split function annotation into return type and argument annotation.

Most of the diffs here are partitioning tests between each new action.

One this one's in, I'll probably take a look at generalising this to class members.

open JetBrains.ReSharper.Plugins.FSharp.Psi.Tree

[<ContextAction(Name = "AnnotateFunctionArgumentTypes", Group = "F#",
Description = "Annotate function with argument types")>]
Copy link
Contributor

@saul saul Nov 15, 2020

Choose a reason for hiding this comment

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

A parameter is a variable in a method definition. When a method is called, the arguments are the data you pass into the method's parameters.

Suggested change
Description = "Annotate function with argument types")>]
Description = "Annotate function parameter types")>]

@auduchinok
Copy link
Member

@mcon Thanks for this PR! We're currently finishing the last things for upcoming 2020.3 release, and these changes should go to 2021.1 EAP instead. I'll create a working net211 branch soon and will review it closer, if you're OK with it.

@mcon
Copy link
Contributor Author

mcon commented Nov 25, 2020

Sounds good to me!

@ForNeVeR
Copy link
Contributor

@mcon, your PR targets net203, but you've merged net211 here. Could you please change the target branch to net211, too?

@mcon mcon changed the base branch from net203 to net211 December 17, 2020 17:55
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

5 participants