feat: add an ability to parse json encoded options

[paulish]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• [+] Feature
• Test
• Docs
• Refactor
• Build-related changes
• Other, please describe:

Description:

I tried to solve the issue #181 using your coding style.

[kevinccbsg]

I really like the implementation @paulish 👏 I was wondering if in future PR we could do something like this.

/**
  * A song
  * @typedef {object} Song
  * @property {string} title - The title
  * @property {string} artist - The artist - json:{"maxLength": 300}
  * @property {number} year - The year - int64 - json:{
  *     "minimum": 2000
  *   }
  */

Like a multiline.

However, the PR looks good to me. Let's wait until @LonelyPrincess or @bri06 ✅ to merge this.

[paulish]

@kevinccbsg I agree that multiline would be a nice addition but it requires more changes to the library and perhaps require some redesign. If this change is accepted we can go ahead and try to implement multiline.

[kevinccbsg]

@all-contributors please add @paulish for code

[allcontributors]

@kevinccbsg

I've put up a pull request to add @paulish! 🎉