[Alarm] Don't raise an error when an alarm without TYPE is found 46/261346/2 accepted/tizen/6.0/unified/20210719.020743 submit/tizen_6.0/20210716.123335
authorPawel Wasowski <p.wasowski2@samsung.com>
Thu, 15 Jul 2021 13:03:15 +0000 (15:03 +0200)
committerPawel Wasowski <p.wasowski2@samsung.com>
Fri, 16 Jul 2021 07:06:33 +0000 (09:06 +0200)
commit426ca38e43e4abe86ac1910cd91283d213b71285
tree4ffd9bb657240fbbb16c6988fcf3e694fb8ae72e
parent2de2af420263912e6cddf19c7405f506825fbe1e
[Alarm] Don't raise an error when an alarm without TYPE is found

tizen.alarm.get() and tizen.alarm.getAll() used to fail when alarms
without "TYPE" property in related app_control existed.
This commit returns such alarms as JS Alarm objects.

[Verification] tct-alarm-tizen-tests (auto): 100 %

I've tested in Chrome DevTools debugger, that when an alarm without
"type" property comes to JS, a valid "Alarm" object is created
(I don't provide any test code snippet, because it required stopping
app in the debugger).

Change-Id: I4b5bcea75509f454bd17b787c080417849720f5a
Signed-off-by: Pawel Wasowski <p.wasowski2@samsung.com>
src/alarm/alarm_api.js
src/alarm/alarm_manager.cc