Skip to content

Conversation

@vasily-kirichenko
Copy link
Contributor

This is how the editor looks (the bug):

image

This is how the preview looks (OK):

image

This is new document text in the debugger (OK):

image

The renaming works correctly as well (I mean it changes the document properly after committing).

So the only place where we have bad behavior is the green spans.

@Pilchie @dsyme Maybe it helps to narrow areas where the bug can sit? Thanks.

@Pilchie
Copy link
Member

Pilchie commented Oct 17, 2017

@dpoeschl or @jasonmalinowski Either of you have any idea?

@jasonmalinowski
Copy link
Member

Just clarifying: does this PR fix the behavior you're seeing (and we're trying to understand why) or fails to do so and we're still trying to understand what's wrong?

@vasily-kirichenko
Copy link
Contributor Author

@jasonmalinowski This PR does not fix the bug.

@vasily-kirichenko
Copy link
Contributor Author

This is how it works at the moment:

1

that is, the renaming itself works, but the preview (green spans) are wrong.

@cartermp
Copy link
Contributor

cartermp commented Jan 2, 2018

@dotnet-bot test this please

Copy link
Contributor

@cartermp cartermp left a comment

Choose a reason for hiding this comment

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

Even though CI was busted previously, this worked for me when I used it. Thanks @vasily-kirichenko

@KevinRansom KevinRansom merged commit 09fc352 into dotnet:master Jan 24, 2018
nosami pushed a commit to xamarin/visualfsharp that referenced this pull request Jan 26, 2022
* do not filter symbol uses by range length in getSymbolUsesInSolution because it causes loosing symbol occurrences in Inline Rename

* make impl closer to the XAML one

* remove obsolete import
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.

6 participants