Generated json doesn't have an array like in the README

[gldraphael]

Command used:

m2j -o index.json -w 0 ./path/*.md

Expected output:

{
  "files": [
    {
      "basename": "hey-there-delilah"
    }
  ]
}

Actual output:

{
  "hey-there-delilah": {
    "basename": "hey-there-delilah"
  }
}

Steps to reproduce:

git clone --branch content --depth 1 https://github.com/hymnsrepo/hymnsrepo-site.git
cd hymnsrepo-site
yarn add --dev markdown-to-json
./node_modules/.bin/m2j -o index.json -w 0 ./hymns/*.md

[scottstanfield]

Oh! Easier to change readme so it doesn’t change other’s expectations but I do prefer “files”. Might need a vote!

…

--- Scott Stanfield [email protected]

On Jan 17, 2018, at 9:06 PM, Galdin Raphael ***@***.***> wrote: Command used: m2j -o index.json -w 0 ./path/*.md Expected output: { "files": [ { "basename": "hey-there-delilah" } ] } Actual output: { "hey-there-delilah": { "basename": "hey-there-delilah" } } Steps to reproduce: git clone --branch content --depth 1 https://github.com/hymnsrepo/hymnsrepo-site.git cd hymnsrepo-site yarn add --dev markdown-to-json ./node_modules/.bin/m2j -o index.json -w 0 ./hymns/*.md — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[gldraphael]

An alternative would be to use an array as the root (in the output):

[
  {
    "basename": "hey-there-delilah"
  }
]

[scottstanfield]

I'm worried about making a breaking change. It would be easier for me to update the readme than change working code. Thoughts? I'd like to close this one out.

[gldraphael]

I think an array would make more sense than the current output. However if you don't feel strongly about it, feel free to close this.

A breaking change would be a major version bump. If you get the time for a v1, do consider this then. (And let me know – I'd like to pitch in.)

[scottstanfield]

Good choice. Will fix on v6 over next few days.