Basically, our basic APIs are based on node.js. They will follow same form with node.js because of compatibility.
However, extended APIs need a guideline because they are implemented by many contributor. (for consistent usability)

Ground Rules

API naming rules

1. The APIs which have similar role should have same API name.
2. Basically, all APIs are async API. If you want to make sync API, you need to add Sync as a suffix.
   For example, readSync(), writeSync(), and so on.

Creating a module object

1. The module object should be generated using open() API for consistent usability.
2. open() API should have configurable as first argument and callback function as second argument.
   callback function is always optional.

For example, GPIO module generate an object like below:

var gpio = require('gpio');
var gpio10 = gpio.open({pin: 10, direction: gpio.DIRECTION.OUT},
                       function(err){console.log(err);});
gpio10.writeSync(1);

Minimize event generation

1. The response of the API call uses callback function.
2. Only generate event when user need to know something without any API call.
3. The event which has similar role should have same event name.

Error generation

1. error can be generated in both JS/native side.
2. The error should be created in the place where it occurs.
3. In the asynchronous function, the first parameter of callback indicates an error. If it is null, the function works without error.

For example, error can be generated like below:

In native side,

iotjs_jargs_t jargs = iotjs_jargs_create(2);

if (!result) {
  iotjs_jargs_append_error(&jargs, "GPIO Error");
}

In JavaScript side,

if (!util.isNumber(value)) {
  throw new TypeError('Bad arguments');
}

Type checking

1. Type checking of API argument is possible both in JS and Native.
2. To prevent type checking multiple times, perform type checking on the first function that receives the variable.
3. Throw error when type checking is failed.

Recommended Rules

1. If it is possible, use the functions provided by libtuv (File open, read, write, etc.)
2. Callback function in API argument should be always optional.