fix: residual space after section causes bad parsing

Any character left on a line after a section should be ignored.
npm · Mar 4, 2021 · 6c70a66 · 6c70a66
1 parent 0522949
commit 6c70a66
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/ini.js b/ini.js
@@ -62,8 +62,8 @@ const decode = str => {
   const out = Object.create(null)
   let p = out
   let section = null
-  //          section     |key      = value
-  const re = /^\[([^\]]*)\]$|^([^=]+)(=(.*))?$/i
+  //          section         |key      = value
+  const re = /^\[([^\]]*)\].*$|^([^=]+)(=(.*))?$/i
   const lines = str.split(/[\r\n]+/g)
 
   for (const line of lines) {

diff --git a/test/fixtures/foo.ini b/test/fixtures/foo.ini
@@ -42,6 +42,9 @@ j = "{ o: "p", a: { av: "a val", b: { c: { e: "this [value]" } } } }"
 cr[] = four
 cr[] = eight
 
+; b section with a space after its title
+[b] 
+
 ; nested child without middle parent
 ; should create otherwise-empty a.b
 [a.b.c]

diff --git a/test/foo.js b/test/foo.js
@@ -51,6 +51,7 @@ var expectD =
          '[]': 'a square?',
          cr: ['four', 'eight'],
          b: { c: { e: '1', j: '2' } } },
+      b: {},
       'x.y.z': {
         'x.y.z': 'xyz',
         'a.b.c': {