pluie-yaml is a vala shared library managing yaml files and yaml nodes in vala language.
Go to file
2018-08-18 23:25:03 +02:00
bin add samples json & yaml + fix flow entries + update build.sh 2018-08-01 14:55:10 +02:00
build initial commit 2018-07-30 18:30:11 +02:00
resources add Yaml.Builder, provide mechanism to populate structure and other GLib.Object derived type 2018-08-18 23:22:08 +02:00
samples add Yaml.Builder, provide mechanism to populate structure and other GLib.Object derived type 2018-08-18 23:22:08 +02:00
src add Yaml.Builder, provide mechanism to populate structure and other GLib.Object derived type 2018-08-18 23:22:08 +02:00
.gitignore fix warning + add doc script 2018-08-07 16:07:13 +02:00
build.sh update meson.build & samples for docker pluie/libyaml image 2018-08-07 21:07:15 +02:00
install.vala.in update meson.build & samples for docker pluie/libyaml image 2018-08-07 21:07:15 +02:00
LICENSE initial commit 2018-07-30 18:30:11 +02:00
meson.build add Yaml.Builder, provide mechanism to populate structure and other GLib.Object derived type 2018-08-18 23:22:08 +02:00
README.md update readme 2018-08-18 23:25:03 +02:00
valadoc.sh fix warning + add doc script 2018-08-07 16:07:13 +02:00

pluie-yaml

pluie-yaml is a vala shared library managing yaml files (v 1.2) and yaml nodes in vala language.
As json is now a valid subset of yaml, you can use this lib to load json files too.

The purpose of this project is to make vala able to load and deal with yaml configuration files.
So, currently the lib deal only with one yaml document (it's not recommended to use multiples doc), but you can use a special ^imports clause (special mapping node) to load a subset of yaml files in the main yaml document.

The lib partially manage tag directives and tag values (basic types and Yaml.Object extended objects types).

pluie-yaml use the libyaml c library (License MIT, many thanks to Kirill Simonov) to parse and retriew related yaml events.

pluie-yaml

legend display_childs :

[ node.name  [refCount]  node.parent.name  node.level  node.ntype.infos ()  node.count ()  node.uuid ]

License

GNU GPL v3

Prerequisites

valac meson ninja libyaml glib gobject gmodule gee pluie-echo

see https://git.pluie.org/pluie/libpluie-echo in order to install pluie-echo-0.2 pkg

Install

git clone the project then cd to project directory and do :

meson --prefix=/usr ./ build
sudo ninja install -C build

Compilation

valac  --pkg pluie-echo-0.2 --pkg pluie-yaml-0.4 main.vala

you can use ./build.sh to rebuild/install the pluie-yaml lib and compile samples files

Api / Documentation

https://pluie.org/pluie-yaml-0.4/index.htm

Docker

a demo image is now available on docker hub. To run a container :

docker run --rm -it pluie/libyaml

then you can execute any samples, for example :

./json-loader

pluie-yaml-json

see pluie/docker-images repository for more details

Usage


config


    var config = new Yaml.Config (path);
    var node   = config.get ("ship-to.address.city{0}");
    if (node != null) {
        of.echo (node.data)
    }

see Finder below to get precisions about config.get parameter (search path definition)


config with ^imports clause

# |  use special key word '^imports' to import other yaml config files in 
# |  current yaml document
# |  '^imports' must be uniq and a direct child of root node
# |  imported files are injected as mapping nodes at top document level
# |  so you cannot use keys that already exists in the document
^imports :
    # you can redefine default import path with the special key '^path'
    # if you do not use it, the default path value will be the current directory
    # redefined path values are relative to the current directory (if a relative path 
    # is provided)
    ^path : ./config
    # you can also define any other var by prefixing key with ^
    ^dir  : subdir
    # and use it enclosed by ^
    # here final test path will be "./config/subdir/test.yml"
    test  : ^dir^/test.yml 
    # here final db path will be "./config/db.yml"
    db    : db.yml

loader

load a single document.
^imports clause is out of effects here.

    var path   = "./config/main.yml";
    // uncomment to enable debug
    // Pluie.Yaml.DEBUG = true;
    var loader = new Yaml.Loader (path /* , displayFile, displayNode */);
    if ((done = loader.done)) {
        Yaml.Node root = loader.get_nodes ();
        root.display_childs ();
    }

finder

pluie-yaml provide a Yaml.Finder to easily retriew a particular yaml node.
Search path definition has two mode.
The default mode is Yaml.FIND_MODE.DOT

  • child mapping node are separated by dot
  • sequence entry must be enclosed in curly brace

ex : grandfather.father.son{2}.age

The Other mode is Yaml.FIND_MODE.SQUARE_BRACKETS

  • node's key name must be enclosed in square brackets
  • sequence entry must be enclosed in curly brace

ex : [grandfather][father][son]{2}[age]

with singlepair node, you can retriew corresponding scalar node with {0}

ex yaml file :

product:
    - sku         : BL394D
      quantity    : 4
      description : Basketball

vala code :

    ...
    var loader = new Yaml.Loader (path, true);
    if ((done = loader.done)) {
        Yaml.Node root = loader.get_nodes ();
        var finder = new Yaml.Finder(root);
        Yaml.Node? node = null;
        if ((node = finder.find ("product{0}.description")) != null) {
            var val = node.val ();
        }
        ...
    }

Traversing

via iterator

    var config = new Yaml.Config (path);
    var root   = config.root_node ();
    if (root != null && !root.empty ()) {
        foreach (var child in root) {
            // do stuff
            of.echo (child.to_string ());
        }
    }

or

    var config = new Yaml.Config (path);
    var root   = config.root_node ();
    if (root != null && root.count () > 0) {
        Iterator<Yaml.Node> it = root.iterator ();
        Yaml.Node? child = null;
        for (var has_next = it.next (); has_next; has_next = it.next ()) {
            child = it.get ();
            // do stuff
            of.echo (child.to_string ());
        }
    }

other

        if (!node.empty ()) {
            Yaml.Node child = node.first();
            of.action("loop throught mapping next sibling", child.name);
            while (child!=null && !child.is_last()) {
                // do stuff
                of.echo (child.to_string ());

                child = child.next_sibling ();
            }
        }
        if (node.count () > 0) {
            child = node.last();
            of.action("loop throught mapping previous sibling", child.name);
            while (child!=null && !child.is_first()) {
                // do stuff
                of.echo (child.to_string ());
                
                child = child.previous_sibling ();
            }
        }

Tag Directives & Tag values

an example is available with samples/yaml-tag.vala sample and resources/tag.yml file

on yaml side, proceed like that :

%YAML 1.2
%TAG !v! tag:pluie.org,2018:vala/
---
!v!Pluie.Yaml.Example test1 :
    myname      : test1object
    type_int    : !v!int 3306
    type_bool   : !v!bool false
    type_char   : !v!char c
    type_string : !v!string mystring1
    type_uchar  : !v!uchar L
    type_uint   : !v!uint 62005
    type_float  : !v!float 42.36
    type_double : !v!double 95542123.4579512128
    !v!Pluie.Yaml.ExampleChild type_object : 
        toto : totovalue1
        tata : tatavalue1
        titi : 123
        tutu : 1

note : only the first level of yaml node matching a vala object need a tag. pluie-yaml has mechanisms to retriew properties types of a Yaml.Object. So basic vala types tag, enum tag, struct tag and derived Yaml.Object (here ExampleChild) or GLib.Object vala tags are not necessary inside a Yaml.Object.

on vala side :

    ...
    var obj = (Yaml.Example) Yaml.Builder.from_node (root.first ());
    of.echo("obj.type_int : %d".printf (o.type_int));
    obj.type_object.method_a ()

pluie-yaml-tag

Builder

pluie-yaml provide a Yaml.Builder which has automatic mechanisms to build Yaml.Object instances (and derived classes) and set basics types properties, enum properties and based Yaml.Object properties from Yaml.node.

Other types like struct or native GLib.Object (Gee.ArrayList for example) properties need some stuff in order to be populated appropriately
We cannot do introspection on Structure's properties, so you need to implement a method which will do the job.

First at all, in the static construct of your class, you need to register (properties) types that need some glue for instanciation.

public class Example : Yaml.Object
{
    static construct
    {
        Yaml.Object.register.add_type (typeof (Example), typeof (ExampleStruct));
        Yaml.Object.register.add_type (typeof (Example), typeof (Gee.ArrayList));
    }
    ...

Secondly you must override the Yaml.Object populate_by_type (Glib.Typem Yaml.Node node) original method.
populate_by_type is called by the Yaml.Builder only if the type property is prealably registered.

Example of implementation from src/vala/Pluie/Yaml.Example.vala :

    public override void populate_by_type(GLib.Type type, Yaml.Node node)
    {
        if (type == typeof (Yaml.ExampleStruct)) {
            this.type_struct = ExampleStruct.from_yaml_node (node);
        }
        else if (type == typeof (Gee.ArrayList)) {
            this.type_gee_al = new Gee.ArrayList<string> ();
            if (!node.empty ()) {
                foreach (var child in node) {
                    this.type_gee_al.add(child.data);
                }
            }
        }
    }

for more details see :

  • src/vala/Pluie/Yaml.Example.vala
  • src/vala/Pluie/Yaml.ExampleChild.vala
  • src/vala/Pluie/Yaml.ExampleStruct.vala
  • samples/yaml-tag.vala

code from samples/yaml-tag.vala :

pluie-yaml-tag

output from samples/yaml-tag.vala :

pluie-yaml-tag


more samples

see samples files in ./samples directory


todo

  • imports clause
  • fix nodes traversing
  • rewrite nodes classes
  • put doc online
  • add docker image
  • manage tag directives & tag (partially done)
  • improve doc
  • dumper