Conflicts with GitLens "Current Line Blame"

[phaseOne]

I finally figured out why one feature, Current Line Blame, of the GitLens extension wasn't appearing; this extension is conflicting with it somehow. If you've got a moment, could you please resolve the conflict, or help me determine next steps for debugging the issue?

Thanks for maintaining this project!

[jeff-hykin]

Hmm I'll look into this. They certainly can be fighting with each other, and I can't think of a good immediate solution. The extension uses VS Code Text Decorations to get the job done, so "text decoration conflict" is probably a general issue.

If you fork the repo, make some changes, and run the Debug: start debugging command, VS Code should open up a new window with those changes enabled and applied. Then in that new window you can go to the help tab and the "Toggle Developer tools" option will allow clicking on elements and diving into the HTML. Sadly though it doesn't give too much insight into the actual VS Code processes that are causing the conflict