fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-07-04 15:36:14 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

update docs

Browse source
This commit is contained in:
sriniv27 2021-02-08 20:13:13 -05:00
parent ac819eb28f
commit 9b80d56773
3 changed files with 26 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

20
features/overrides.feature
View file

@ -2,9 +2,17 @@ Feature: Implementing Runtime Overrides for Select Configuration Keys
Scenario: Override configured editor with built-in input === editor:''
Given we use the config "tiny.yaml"
When we run jrnl with --config-override editor ''
Then the stdin prompt must be launched
When we run "jrnl --config-override editor ''"
Then the stdin prompt should have been called
Scenario: Postconfig commands with overrides
Given We use the config "basic_encrypted.yaml"
And we use the password "test" if prompted
When we run "jrnl --decrypt --config-override highlight false --config-override editor nano"
Then the runtime config should have "encrypt" set to "false"
And the runtime config should have "highlight" set to "false"
And the editor "nano" should have been called
@skip_win
Scenario: Override configured linewrap with a value of 23
Given we use the config "tiny.yaml"
@ -30,13 +38,13 @@ Feature: Implementing Runtime Overrides for Select Configuration Keys
@skip_win
Scenario: Override color selections with runtime overrides
Given we use the config "tiny.yaml"
When we run jrnl with -1 --config-override colors.body blue
When we run "jrnl -1 --config-override colors.body blue"
Then the runtime config should have colors.body set to blue
@skip_win
Scenario: Apply multiple config overrides
Given we use the config "tiny.yaml"
When we run jrnl with -1 --config-override colors.body green --config-override editor "nano"
When we run "jrnl -1 --config-override colors.body green --config-override editor 'nano'"
Then the runtime config should have colors.body set to green
And the runtime config should have editor set to nano
@ -44,7 +52,7 @@ Feature: Implementing Runtime Overrides for Select Configuration Keys
@skip_win
Scenario Outline: Override configured editor
Given we use the config "tiny.yaml"
When we run jrnl with --config-override editor "<editor>"
When we run "jrnl --config-override editor \"<editor>\""
Then the editor <editor> should have been called
Examples: Editor Commands
| editor |