Allow YAML format for .netkans

[HebaruSan]

Motivation

See KSP-CKAN/CKAN#3367, we might want to allow .netkans to use YAML format. If so, the metadata-webtool should take advantage of it by generating YAML.

Changes

• The JS-YAML library is loaded (its functions go into jsyaml)
• JSON.stringify is replaced with jsyaml.dump
• JSON.parse is replaced with jsyaml.load

This will make the webtool generate YAML if merged.

[DasSkelett]

spec_version: v1.16
identifier: 4kSPExpanded
license: MIT
$kref: '#/ckan/spacedock/2554'
resources:
  homepage: >-
    https://forum.kerbalspaceprogram.com/index.php?/topic/197794-18x-19x-110x-4ksp-expanded/
  repository: https://github.com/linuxgurugamer/4ksp_Expanded
conflicts:
  - name: 4kSP
depends:
  - name: ToolbarControllerClickThroughBlocker
x_via: Generated by Metadata Webtool

Heh, I think we can avoid the conversion to multi-line strings for the homepage with the lineWidth option:
https://github.com/nodeca/js-yaml#dump-object---options-

Question is to what value, multi-line strings might be handy for hard-coded abstracts. 120, maybe?

[HebaruSan]

Works better with a truncated URL:

spec_version: 1
identifier: 4kSPExpanded
abstract: >-
  4kSP scales the map elements corresponding to the stock UI scale setting

  4kSP scales the map elements corresponding to the stock UI scale setting. The
  UI scale slider can be found under Settings > General > UI-Scale. There is
  also a small window which you can chagne the sizes while the mapview is being
  displayed

  4kSP scales the map elements corresponding to the stock UI scale setting. The
  UI scale slider can be found under Settings > General > UI-Scale. There is
  also a small window which you can chagne the sizes while the mapview is being
  displayed

  4kSP scales the map elements corresponding to the stock UI scale setting. The
  UI scale slider can be found under Settings > General > UI-Scale. There is
  also a small window which you can chagne the sizes while the mapview is being
  displayed
license: MIT
$kref: '#/ckan/spacedock/2554'
resources:
  homepage: https://forum.kerbalspaceprogram.com/index.php?/topic/197794-*
  repository: https://github.com/linuxgurugamer/4ksp_Expanded
conflicts:
  - name: 4kSP
depends:
  - name: ToolbarController
  - name: ClickThroughBlocker
x_via: Generated by Metadata Webtool

I suppose this mildly encourages shorter URLs, but if not, we can always edit to taste in the NetKAN PR.

Question is to what value, multi-line strings might be handy for hard-coded abstracts. 120, maybe?

If we're going to have a characters-per-line limit (and I think we should), the default of 80 makes sense to me. It's widely supported and historically grounded, and makes for relatively comfortable reading.

[DasSkelett]

I suppose this mildly encourages shorter URLs, but if not, we can always edit to taste in the NetKAN PR.

Fair enough

[DasSkelett]

Appears to work the way it should