![]() This PR fixes a bug where breakpoints would be rendered on incorrect lines when openings a git hunk that contained breakpoints. This also disables breakpoints from being shown in deleted git hunks as well. Note: There's some unexpected behavior when using an anchor to get a display point that is in an open git hunk, where the `anchor.to_point().col == 0`. ```rust let position = multi_buffer_anchor .to_point(&multi_buffer_snapshot) .to_display_point(&snapshot); ``` The above code will return a display point that is one line below where the anchor actually represents when it's in an opened hunk diff. Which causes the bug shown below https://github.com/user-attachments/assets/bd15d02a-3cdc-4c8e-841f-bef238583351 @ConradIrwin Is this expected behavior when calling `.to_display_point(&snapshot)`? Release Notes: - N/A |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
LICENSE-GPL |