fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-05-20 04:58:32 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

formatting

Browse source
This commit is contained in:
Suhas 2021-01-27 18:14:08 -05:00
parent b2a60fd297
commit e85300eced
1 changed files with 38 additions and 44 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

82
features/overrides.feature
View file

@ -1,53 +1,47 @@
Feature: Implementing Runtime Overrides for Select Configuration Keys Feature: Implementing Runtime Overrides for Select Configuration Keys
Scenario: Override configured editor with built-in input === editor:'' Scenario: Override configured editor with built-in input === editor:''
Given we use the config "editor-args.yaml" Given we use the config "tiny.yaml"
When we run jrnl with --config-override editor:"" When we run jrnl with --config-override editor:''
Then the editor "" should have been called Then the stdin prompt must be launched
Scenario Outline: Override configured editor @skip_win
Given we use the config "editor.yaml" Scenario: Override configured linewrap with a value of 23
When we run jrnl with --config-override editor:"<editor>" Given we use the config "tiny.yaml"
Then the editor "<editor>" should have been called When we run "jrnl -2 --config-override linewrap:23 --format fancy"
Examples: Editor Commands Then the output should be
|editor|
|nano|
|vi -c startinsert|
|code -w - |
@skip_win """
Scenario: Override configured linewrap with a value of 23 ┎─────╮2013-06-09 15:39
Given we use the config "editor.yaml" ┃ My ╘═══════════════╕
When we run "jrnl -2 --config-override linewrap:23 --format fancy" ┃ fir st ent ry. │
Then the output should be ┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
""" ┃ Everything is │
┎─────╮2013-06-09 15:39 ┃ alright │
┃ My ╘═══════════════╕ ┖─────────────────────┘
┃ fir st ent ry. │ ┎─────╮2013-06-10 15:40
┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤ ┃ Lif ╘═══════════════╕
┃ Everything is │ ┃ e is goo d. │
┃ alright │ ┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
┖─────────────────────┘ ┃ But I'm better. │
┎─────╮2013-06-10 15:40 ┖─────────────────────┘
┃ Lif ╘═══════════════╕ """
┃ e is goo d. │
┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤ @skip_win
┃ But I'm better. │ @wip
┖─────────────────────┘ 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
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,editor:"nano"
Then the runtime config should have colors.body set to green
And the runtime config should have editor set to nano
@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'
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,editor:"nano"
Then the runtime config should have colors.body set to green
And the runtime config should have editor set to nano
Scenario Outline: Override configured editor Scenario Outline: Override configured editor
Given we use the config "tiny.yaml" Given we use the config "tiny.yaml"
When we run jrnl with --config-override editor:"<editor>" When we run jrnl with --config-override editor:"<editor>"