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

Visual Basic support #15

Merged
merged 2 commits into from
Nov 19, 2014
Merged

Conversation

sharwell
Copy link
Member

This pull request adds the Visual Basic support implemented by @AdamSpeight2008. Fixes #6.

@tugberkugurlu
Copy link
Contributor

I guess file renames wiped all file history but there is nothing to do there 😞 looks good to me.

@sharwell
Copy link
Member Author

Must be a GitHub limitation of anything. Git itself has no trouble tracking files through the rename here, even for operations like rebase.

@tugberkugurlu
Copy link
Contributor

I cannot seem to get it working when I F5 to test it inside the experimental hive:

screenshot 2014-11-19 14 18 38

Am I doing something wrong?

@tugberkugurlu
Copy link
Contributor

It seems that the problem is the node target. It only sees the node as ParameterSyntax when you select the whole parameter:

screenshot 2014-11-19 14 23 40

I would assume to get the refactoring suggestion when my cursor is around the parameter name as below but the node seems to be the ModifierIdentiferSyntax:

screenshot 2014-11-19 14 23 29

' Note: If I can find the nameof feature in VB.net, then I'll change this line to reflect that
Dim _paramname_ = SyntaxFactory.StringLiteralExpression(
SyntaxFactory.StringLiteralToken("""" & parameterStmt.Identifier.Identifier.Text & """",
parameterStmt.Identifier.Identifier.Text))
Copy link
Contributor

Choose a reason for hiding this comment

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

do we have nameof operator in VB?

Copy link
Member Author

Choose a reason for hiding this comment

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

I would suggest making this a follow-up issue.

Copy link
Contributor

Choose a reason for hiding this comment

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

👍

@sharwell
Copy link
Member Author

Is there anything here that still needs to be fixed prior to the initial "merge"? Since the request contains file moves it helps to include it early so people can work from a new reference point.

@tugberkugurlu
Copy link
Contributor

@sharwell Can we do something for this (I have no idea if it's safe to watch for ModifierIdentiferSyntax node instead of ParameterSyntax)? #15 (comment)

It seems pretty annoying but if this is the way it should be, :shipit:

@sharwell
Copy link
Member Author

If the behavior is unintuitive we can file a separate issue.

@tugberkugurlu
Copy link
Contributor

That's fine, I'm getting it in then. I will open up the issues as well.

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.

Support for Visual Basic
3 participants