add option to modify gpio base path for testing purposes

[sa-linetco]

No description provided.

[rzr]

Maybe you'll be interested in:
#42

[rzr]

Please rebase and send cleanup patches separately.

[sa-linetco]

@rzr there you go :)

[rzr]

Thx,
Please preserve current style, or send a patch that just reindent (using clang-format?) current sources and then add a feature patch on it

[EnotionZ]

From a software design perspective, I think it makes more sense to set the base directory path on the class method. On an instance level, the test option should be the filename which contains the value rather than the directory.

Also this is probably unintentional but the entire package.json file is overridden which may cause reference problems when it's publish in npm.

[rzr]

please keep the var vs const and fix conflict then I think it can be mergeable

[rzr]

this one is fine,

[rzr]

please split this PR in several PR with smaller changes

[rzr]

do we want to change author ? here

[rzr]

Please try to split this change is smaller PR

[rzr]

Is there any interest to upstream this for next release ?

[rzr]

Maybe you can try to demonstrate this by controlling on board leds : ie

emulate actions in:
/$dir/sys/class/gpio/gpio35

would be forwarded to:
/sys/class/leds/led0/brightness

does it make sense ?

[EnotionZ]

@rzr I think I see where you're getting at - it's like rather than (or in addition to) having a direct path, developers can specify a more powerful mapping. I like it, should be considered in #51.