Enum will help with problems

[cesarjhony]

I dispend many of time searching bugs in my code, and when I found was a problem like:
pin.writeSync(true); //not work
pin.writeSync(1); //work fine
pin.writeSync(Gpio.HIGH); //work fine, but ENUM is not a Standard in your lib.
But, I and the most of devs use autocomplete, like a VS Code. With the STATIC or ENUM constants might save the day, the assistents find there and show us the options.
Please add all options like a static.
Your framework is amazing, but it still may be better.

[fivdi]

@cesarjhony Thank you for suggesting this improvement. I'll take a look to see what can be done to improve things.

[johntalton]

Ive used HIGH / LOW in my work, as exported here:

onoff/onoff.js

Line 343 in 07d36e2

Gpio.HIGH = HIGH;

while the TS version does something a bit different:

onoff/onoff.d.ts

Line 1 in 07d36e2

export type High = 1;

I would suggest that the js->d.ts is a stub solution at this point and there the BinaryValue type exists.

Anything to aid in the correctness / clearness / ease of use would be interesting as many libraries "export" this type of const FOO = x / Klazz.FOO = FOO style pattern. @cesarjhony Could you expand on your desired Use Case?

[cesarjhony]

My usage was just:
HIGH, LOW, IN, OUT;

I don't know if will better to be grouped style like:
Gpio.Level={ HIGH, LOW };
Gpio.Direction={ OUT, IN };

Thank you very much for appreciate my opinion 😊, but I have no better ideas.