[Alarm] Don't raise an error when an alarm without TYPE is found 09/261409/1
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 09:54:42 +0000 (09:54 +0000)
commitde9d976f937ad08e83b7b2ae6d0b3a13b95239ed
tree400851ae547ad2ea8cbb905bf3fe496e913dcc04
parenta296a6b8ba71d36c06f266f634db6c152d17da68
[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