-
Notifications
You must be signed in to change notification settings - Fork 205
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
Bump ghcide #3865
Bump ghcide #3865
Conversation
@@ -584,8 +584,7 @@ goToDefinitionTests mbScenarioService = Tasty.testGroup "Go to definition tests" | |||
expectGoToDefinition (foo,2,[2..4]) Missing -- " : " | |||
expectGoToDefinition (foo,2,[9]) Missing -- "\n" | |||
expectGoToDefinition (foo,2,[10]) Missing -- (out of range) | |||
expectGoToDefinition (foo,3,[0..2]) (At (foo,3,0)) -- "foo" | |||
expectGoToDefinition (foo,3,[3..5]) Missing -- " = " | |||
expectGoToDefinition (foo,3,[0..5]) (At (foo,3,0)) -- "foo = " |
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.
I think the new behavior here actually makes more sense, we are still within the definition of foo
at the equal sign so it makes sense for goto definition to point back to foo
.
@@ -645,13 +644,11 @@ goToDefinitionTests mbScenarioService = Tasty.testGroup "Go to definition tests" | |||
, "baz = 10" | |||
] | |||
setFilesOfInterest [foo] | |||
expectGoToDefinition (foo,2,[0..2]) (At (foo,2,0)) | |||
expectGoToDefinition (foo,2,[3..5]) Missing | |||
expectGoToDefinition (foo,2,[0..5]) (At (foo,2,0)) |
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.
Same here.
260741b
to
1d009e9
Compare
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.
LGTM thank you
Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tags, if appropriateNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.