[v2] Yaml and JSON parser

[HotKeyIt]

Yaml on github

Parses Yaml and JSON documents from string or file. Requires AutoHotkey v2.106+

Most of Yaml 1.2 spec are implemented:

• Mapping between Sequences is not supported, see Example 2.11.
• Only tags !!str, !!int, !!float, !!binary, !!bool and !!null are supported. !!set results in error and all other tags are ignored.
• Only Yaml documents with 1000 level deepness can be parsed (to increase simply increase Loop 1000 in Load(ByRef txt,Y:=0)
• Other features might be not implemented.
• Yaml uses objects for map and arrays for sequence, however Dump will work for Array, Map and Object.

How to use:

• Create an Object from Text or File:
  YamlObj:=Yaml(TextOrFilePath)
• Apply/combine another Yaml document into existing object:
  Yaml(TextOrFilePath, YamlObject)
• Dump Yaml object back to text, use JSON from 5-th level only:
  Yaml(YamlObject, 5)
• Dump Yaml object back to text, use JSON only and indent until 5-th level (v1.0.4++):
  Yaml(YamlObject, -5)
• Yaml(TextOrFilePath) will result in Array of documents (objects), if you have only one document you can retrieve it directly:
  YamlObj:=Yaml(TextOrFilePath)[1]

Full length examples from yaml.org:

Code: Select all

text:="
(
--- !<tag:clarkevans.com,2002:invoice>
invoice: 34843
date   : 2001-01-23
bill-to: &id001
    given  : Chris
    family : Dumars
    address:
        lines: |
            458 Walkman Dr.
            Suite #292
        city    : Royal Oak
        state   : MI
        postal  : 48046
ship-to: *id001
product:
    - sku         : BL394D
      quantity    : 4
      description : Basketball
      price       : 450.00
    - sku         : BL4438H
      quantity    : 1
      description : Super Hoop
      price       : 2392.00
tax  : 251.42
total: 4443.52
comments:
    Late afternoon is best.
    Backup contact is Nancy
    Billsmer @ 338-4338.
---
Time: 2001-11-23 15:01:42 -5
User: ed
Warning:
  This is an error message
  for the log file
---
Time: 2001-11-23 15:02:31 -5
User: ed
Warning:
  A slightly different error
  message.
---
Date: 2001-11-23 15:03:17 -5
User: ed
Fatal:
  Unknown variable "bar"
Stack:
  - file: TopClass.py
    line: 23
    code: |
      x = MoreObject("345\n")
  - file: MoreClass.py
    line: 58
    code: |-
      foo = bar

)"
y:=Yaml(text) ; Load Yaml documents into objects
MsgBox Yaml(y,5) ; Dump objects back into Yaml

[kczx3]

FYI there is a dedicated sub forum for v2 scripts and functions

[HotKeyIt]

Thanks, topic moved.

[HotKeyIt]

Fixed a bug and Alias for objects

[HotKeyIt]

• Intendation increased to 1000, can be easily increased if necessary.
• Implemented multi-intend so examples from yaml.org work out of the box
• Implemented multi document support, see example
• Implemented plain scalar

[HotKeyIt]

• Fixed bug in Dump
• Fixed bug in JSON parser

[kczx3]

The main title of this says "[v2] Yaml and JSON parser". What part of this parses JSON?

[guest3456]

The main title of this says "[v2] Yaml and JSON parser". What part of this parses JSON?

my guess from his yaml spec link:

YAML can therefore be viewed as a natural superset of JSON, offering improved human readability and a more complete information model. This is also the case in practice; every JSON file is also a valid YAML file. This makes it easy to migrate from JSON to YAML if/when the additional features are required.

JSON's RFC4627 requires that mappings keys merely “SHOULD” be unique, while YAML insists they “MUST” be. Technically, YAML therefore complies with the JSON spec, choosing to treat duplicates as an error.

---

would be nice to see some unit testing supplied with libraries like this

[kczx3]

Interesting... So this could parse a JSON string just fine... I'm intrigued now. I think that the heading may throw people off because JSON is probably a more familiar term and format for people of this forum.

I assume that when you dump it though that it will be in yaml format and not the original JSON format.

[HotKeyIt]

• Implemented pure JSON parsing and proper dumping, to beautify (indent) JSON use negative second parameter

Yaml(YamlObject, -5)

[HotKeyIt]

Interesting... So this could parse a JSON string just fine... I'm intrigued now. I think that the heading may throw people off because JSON is probably a more familiar term and format for people of this forum.

I assume that when you dump it though that it will be in yaml format and not the original JSON format.

Now it should fully support in Yaml and JSON as well as in and out

[kczx3]

• Implemented pure JSON parsing and proper dumping, to beautify (indent) JSON use negative second parameter

Yaml(YamlObject, -5)

Sorry but I’m not seeing that anywhere. I went to your GitHub repo for this however it doesn’t show as being updated for two years.

Never mind. Seems like you’re using the quote feature to post release notes. I wasn’t quite getting that. Apologies.

[HotKeyIt]

Sorry, I have updated GitHub as well

[coffee]

return Load(FileRead(file),Yaml) ; load yaml from file This is referencing the wrong variable.

[HotKeyIt]

Thanks, this is fixed now.

[kczx3]

Coffee, was that issue what was causing the speed issues with this parser that you mentioned in another thread?

[HotKeyIt]

I had a look and AFAIK, the biggest speed issue is due to Yaml parsing char by char.
In Yaml notation it is allowed to use unquoted keys and values while JSON needs to be enclosed in quotes.

I will need to implement a separate function to parse pure JSON faster.

[coffee]

Coffee, was that issue what was causing the speed issues with this parser that you mentioned in another thread?

Nop.

[HotKeyIt]

Pure JSON are now parsed separately very fast
Increased speed for Yaml and some bugfixes

v1.0.6
Fix double quotes

[HotKeyIt]

Improved performance and some bugfixes