Skip to content

Extract parameter based on a value within a method #49577

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

Open
Tracked by #55825
keertip opened this issue Aug 1, 2022 · 3 comments
Open
Tracked by #55825

Extract parameter based on a value within a method #49577

keertip opened this issue Aug 1, 2022 · 3 comments
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-refactoring Issues with analysis server refactorings P4 type-enhancement A request for a change that isn't a bug

Comments

@keertip
Copy link
Contributor

keertip commented Aug 1, 2022

The ability to extract a value/variable within a method as parameter of the method. This is available for Java/Kotlin.

@keertip keertip added legacy-area-analyzer Use area-devexp instead. devexp-refactoring Issues with analysis server refactorings type-enhancement A request for a change that isn't a bug P4 labels Aug 1, 2022
@bwilkerson
Copy link
Member

@mosuem mosuem added the good first issue A good starting issue for contributors (issues with this label will appear in /contribute) label May 23, 2024
@userAdityaa
Copy link

Hey, can you explain me what do you mean by extracting paramter based on a value method Im finding it difficult understanding. If you could explain me, I think I can solve this up for a good first issue.

@bwilkerson
Copy link
Member

I think that what we mean is not yet well defined, other than to provide something similar to what some other tools provide. The link in a previous comment points to one such tool, but I suspect that there are others and we should start by surveying what's available elsewhere, then deciding what we want to provide. The design will need to take into account the fact that we're currently quite limited in what a refactoring can request in the way of user input.

However, I disagree with the "good first issue" label. Refactorings (that require user input) are typically harder than fixes or assists (refactorings that don't require user input), so I would encourage you to try learning about this aspect of the analysis server with a simpler fix or assist.

@bwilkerson bwilkerson removed the good first issue A good starting issue for contributors (issues with this label will appear in /contribute) label Jun 3, 2024
@bwilkerson bwilkerson added area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. and removed legacy-area-analyzer Use area-devexp instead. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-refactoring Issues with analysis server refactorings P4 type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

4 participants