From e85300eced5644fd525efdc6f2de5e80e379c6bb Mon Sep 17 00:00:00 2001
From: Suhas <sugas182@gmail.com>
Date: Wed, 27 Jan 2021 18:14:08 -0500
Subject: [PATCH] formatting

---
 features/overrides.feature | 82 ++++++++++++++++++--------------------
 1 file changed, 38 insertions(+), 44 deletions(-)

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