Skip to content

Conversation

@CyrusNajmabadi
Copy link
Member

Cleanup work in the extract method codebase before doign some more major feature work. I've documented int eh PR what changes i'm making. Should be reviewed with whitespace off.

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner December 22, 2024 04:03
@ghost ghost added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 22, 2024
</data>
<data name="Cannot_determine_valid_range_of_statements_to_extract" xml:space="preserve">
<value>Cannot determine valid range of statements to extract</value>
</data>
Copy link
Member Author

Choose a reason for hiding this comment

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

Moved to shared location so we can have one string for VB and C#

@CyrusNajmabadi
Copy link
Member Author

@JoeRobich @ToddGrun PTAL. This is one of many cleanup PRs i'm making this area as i modernize and simplify the code on the way to some larger user-facing feature refactorings. Note: if you have further suggestions, i'm happy to incorporate them into the followup PRs that are waiting on this one. Thanks!

}
private static object NewMethod(object p2)
private static global::System.Object NewMethod(global::System.Object p2)
Copy link
Member Author

Choose a reason for hiding this comment

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

intentional change. EM now calls trhough the correct syntax generator code. but the tests don't actually run the simplification pass (since the tests unfortunately test parts of the api directly).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead VSCode

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants