mirror of
https://github.com/jesseduffield/lazygit.git
synced 2025-02-07 13:42:01 +02:00
f3eb180f75
We're not fully standardising here: different contexts can store their range state however they like. What we are standardising on is that now the view is always responsible for highlighting the selected lines, meaning the context/controller needs to tell the view where the range start is. Two convenient benefits from this change: 1) we no longer need bespoke code in integration tests for asserting on selected lines because we can just ask the view 2) line selection in staging/patch-building/merge-conflicts views now look the same as in list views i.e. the highlight applies to the whole line (including trailing space) I also noticed a bug with merge conflicts not rendering the selection on focus though I suspect it wasn't a bug with any real consequences when the view wasn't displaying the selection. I'm going to scrap the selectedRangeBgColor config and just let it use the single line background color. Hopefully nobody cares, but there's really no need for an extra config.
23 lines
851 B
YAML
23 lines
851 B
YAML
# This config is used in our integration tests. If we want to modify this for a specific test, you can do so in the SetupConfig function
|
|
|
|
disableStartupPopups: true
|
|
promptToReturnFromSubprocess: false
|
|
|
|
gui:
|
|
theme:
|
|
activeBorderColor:
|
|
- green
|
|
- bold
|
|
inactiveBorderColor:
|
|
- black
|
|
# Not important in tests but it creates clutter in demos
|
|
showRandomTip: false
|
|
animateExplosion: false # takes too long
|
|
git:
|
|
# We don't want to run any periodic background git commands because it'll introduce race conditions and flakiness.
|
|
# If we need to refresh something from within the test (which should only really happen if we've invoked a
|
|
# shell command in the background) we should have the user press shift+R to refresh.
|
|
# TODO: add tests which explicitly test auto-refresh functionality
|
|
autoRefresh: false
|
|
autoFetch: false
|