search

gitkraken / vscode-gitlens

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
http://gitkraken.com/gitlens
Other
9.03k stars 1.35k forks source link

Setting heatmap's `coldColor` and `hotColor` breaks file blame & related functionality #1205

Closed robertrossmann closed 3 years ago

robertrossmann commented 3 years ago

Steps to Reproduce:

  1. Set a non-default value for either gitlens.heatmap.coldColor or gitlens.heatmap.hotColor
  2. Toggle File Blame Annotations
  3. Observe no blame annotations appearing in current file
  4. Observe the following error message in GitLens' Output panel: 
    TypeError: (intermediate value).scale is not a function

When these two colour values do not match the defaults the code branches here. For some reason the imported chroma-js module does not have a .scale() function which causes this error. I am not sure what's happening with that module, why the .scale function is not available. 🤷‍♂️

robertrossmann commented 3 years ago

😍 👍

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.