-
Notifications
You must be signed in to change notification settings - Fork 708
Add FAR across razor and cs files #8250
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
await integrationHelpers.waitForExpectedResult<vscode.Location[]>( | ||
async () => | ||
await vscode.commands.executeCommand( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this done in waitForExpectedResults in order to retry? Generally awaiting the command should return the results
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, it's just for the retry logic. Since this now is actually using project information instead of misc project it can happen before syncing csharp if the test runs too fast.
Renames tests to reference instead of definition, but I kept the definition test there since it's sort of under the umbrella of that and naming is hard.
Adds a new test that uses a code behind to find references that exist in both cs and razor.
Found an issue with why some tests are hard to write. I added documentation of my findings but haven't found a good solution, just a workaround to avoid getting into that state. We'll see how bad that gets because it may mean that tests will race against eachother. It also may mean my fix isn't really a fix at all and we'll need something better...