simple_json_reader: privately imports lexer&parser

So public API is easier to read.

Signed-off-by: Jean Privat <jean@pryen.org>
lib/github_api: new lib to access the github api

Signed-off-by: Jean Privat <jean@pryen.org>
contrib/github_search_for_jni: update to use github_api

Signed-off-by: Jean Privat <jean@pryen.org>
contrib: add `github_merge` the script I use to produce merge of PR

Signed-off-by: Jean Privat <jean@pryen.org>
tests: add github_merg

Signed-off-by: Jean Privat <jean@pryen.org>
Merge: github_merge tool

Extraction of the github API in its own lib and rewrite of my nodejs script in pure Nit

Pull-Request: #409
Reviewed-by: Alexis Laferrière <alexis.laf@xymus.net>
toolcontext: add nit_dir service

Use `NIT_DIR` or some heuristic to find the Nit directory.
In next commits, tools will use it.

Signed-off-by: Jean Privat <jean@pryen.org>
src: adapt tools to use `ToolContext::nit_dir` instead of `NIT_DIR`

Signed-off-by: Jean Privat <jean@pryen.org>
nitunit: learn to use `nit_dir` instead of hardcoding the path of nitg

Signed-off-by: Jean Privat <jean@pryen.org>
tests: update sav related to `cannot find module` errors

The lib directory is not duplicated since the single nitdir player

Signed-off-by: Jean Privat <jean@pryen.org>
mkcsrc: fix a regexp that brokes the reboostrap

Signed-off-by: Jean Privat <jean@pryen.org>
Merge: `nit_dir` as a service

ToolContext exposes a `nit_dir` service that tools can use.
It is so good that, now, the `bin` directory can be directly put in the PATH on most system while `NIT_DIR` is unset.

Previous direct users of `NIT_DIR` are transformed to use the new service.
Also, `nitunit` uses the new service to find the compiler instead of a hard-coded path.

Closes #392
Closes #408

Pull-Request: #412
Reviewed-by: Alexis Laferrière <alexis.laf@xymus.net>
Reviewed-by: Alexandre Terrasa <alexandre@moz-code.org>
nitunit: more verbose on execution

prints the generated file name and some statistics.

Signed-off-by: Jean Privat <jean@pryen.org>
nitunit: add option `--no-act` that does noes run the units

It just analyses and extract units.

Signed-off-by: Jean Privat <jean@pryen.org>
nitunit: lower verbosity level to track each execution of test

Signed-off-by: Jean Privat <jean@pryen.org>
markdown: understang github fencing

~~~~
blabla
~~~
code
~~~
blabla
~~~~

Signed-off-by: Jean Privat <jean@pryen.org>
parser_util: fix and nitunitfy `parse_something`

Signed-off-by: Jean Privat <jean@pryen.org>
niti: force `eval` to parse things as modules.

Signed-off-by: Jean Privat <jean@pryen.org>
nitunit: allows multiple independant block in a single comment

A new block is started by non-trivial modules

Signed-off-by: Jean Privat <jean@pryen.org>
nitunit: `-W` warns fishy block in comments

Usefull to find buggy nitunit tests with the `--no-act` flag.

Signed-off-by: Jean Privat <jean@pryen.org>