[Alarm] Fixing AlarmRelative/Absolute .period 21/117821/4
authorSzymon Jastrzebski <s.jastrzebsk@partner.samsung.com>
Mon, 13 Mar 2017 10:31:34 +0000 (11:31 +0100)
committerSzymon Jastrzebski <s.jastrzebsk@partner.samsung.com>
Mon, 13 Mar 2017 10:31:34 +0000 (11:31 +0100)
commit18afa4ce89f133e378f7e0bb0f26b4b4de9d71d3
tree787c15d6e603df6081b8b6c10b93bb5389aa1ac2
parentdc80f733c10e3aa6e368e64df079602e4564aeab
[Alarm] Fixing AlarmRelative/Absolute .period

When alarm.period wasn't set by user,
tizen.alarm.getAll()/get() should set alarm.period to null, not 0.
After adding alarm period is updated.

[Verification] TCTs passed 59/1/0/0
Failing test case needs to be fixed

Change-Id: I800477b4cefbdfe152b7abb0db750b6713cd0ed3
Signed-off-by: Szymon Jastrzebski <s.jastrzebsk@partner.samsung.com>
src/alarm/alarm_api.js
src/alarm/alarm_manager.cc